Robert: How about grabbing a random person, setting them in front of chromium, telling them "I need you to do some UX testing for me. This is about testing the program and not about testing you, you cannot do anything wrong. Up here we have the history menu. What would you expect what happens if you click any of these recently closed items? […] Now click it. Did what just happened make sense to you? Kthxbye", and repeating this about 3 times? (for both behaviors) If all participants feel the same way, go with that and cite "user experience research". Should take < 20 minutes.
On Thu, Aug 13, 2009 at 9:18 AM, Pam Greene<[email protected]> wrote: > They always felt pretty different to me. In one case, I'm undoing something > I did, and I expect the state to be restored to how it was. In the other, > I'm initiating a new action, and I expect the behavior to be the same as for > bookmarks. > > - Pam > > On Thu, Aug 13, 2009 at 6:50 AM, Mike Pinkerton <[email protected]> > wrote: >> >> As a Chrome developer, I understand the difference, but "undo closed >> tab" is just the most recent tab, where we have the 5 most recently >> closed tabs in the history menu. From a user perspective, why should >> one be different than the other? Why do I only get a new tab when I'm >> undoing the last tab, and not 2 or 3 tabs ago? Just because in code >> they're different, and that seems wrong. >> >> On Wed, Aug 12, 2009 at 5:53 PM, Pam Greene<[email protected]> wrote: >> > You want undo-close-tab for that use case, not history. The >> > where-to-open >> > behavior of undo-close-tab is completely different. Agreed that there's >> > some >> > overlap in usage, though. >> > - Pam >> > >> > On Wed, Aug 12, 2009 at 12:59 PM, Mike Pinkerton >> > <[email protected]> >> > wrote: >> >> >> >> The few times I've needed to use the history menu (gak, i just closed >> >> something by accident, let me get it back), re-using the current tab >> >> is exactly what i don't want, as it clobbers something totally >> >> unrelated that I had open. That's what prompted this discussion. >> >> >> >> I agree that it should behave like bookmarks in theory, since it's >> >> effectively the same presentation, but it seems to get in the way of >> >> my workflow when I try to actually use it. >> >> >> >> On Wed, Aug 12, 2009 at 3:33 PM, Scott Violet<[email protected]> wrote: >> >> > >> >> > I would suggest you create something like browser/views/event_utils >> >> > on >> >> > the Mac (and Linux) side. Any place you're opening a URL from a user >> >> > gesture you map the event to a WindowOpenDisposition. This way the UI >> >> > is consistent with regards to what user gestures do. >> >> > >> >> > As to this particular case, I believe the default should be current >> >> > tab. >> >> > >> >> > -Scott >> >> > >> >> > On Wed, Aug 12, 2009 at 12:23 PM, Brett Wilson<[email protected]> >> >> > wrote: >> >> >> >> >> >> On Wed, Aug 12, 2009 at 12:18 PM, Avi Drissman<[email protected]> >> >> >> wrote: >> >> >>> Brett— >> >> >>> >> >> >>> Are we talking about the history page, or history items? The >> >> >>> history >> >> >>> page >> >> >>> gets its own tab, sure. But when someone picks an item from the >> >> >>> history >> >> >>> menu, where does it go? I think current foreground tab is right, >> >> >>> with >> >> >>> command for background tabs. >> >> >> >> >> >> Yes, I was confused. I think clobbering is OK in that case. My new & >> >> >> improved opinion is it should act like the drop-down on the >> >> >> back/forward menus. >> >> >> >> >> >> Brett >> >> >> >> >> >> > >> >> >> >> >> > >> >> > > >> >> > >> >> >> >> >> >> >> >> -- >> >> Mike Pinkerton >> >> Mac Weenie >> >> [email protected] >> >> >> >> >> >> > >> > >> >> >> >> -- >> Mike Pinkerton >> Mac Weenie >> [email protected] > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
