"…and repeat 3 times, for each version" gives you six opinions – and
"uninvolved" opinions, too.
On Thu, Aug 13, 2009 at 10:43 AM, Glen Murphy wrote:
> I think you'd need more than one person and twenty minutes. One person
> isn't going give you any useful data - this thread is full of
> one-pers
I think you'd need more than one person and twenty minutes. One person
isn't going give you any useful data - this thread is full of
one-persons.
I happen to agree with Pink, though I think there should be less
difference between History and Closed Items (I have a long running
rant about how afte
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 y
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 wrote
On Thu, Aug 13, 2009 at 11:08, Julian Harris wrote:
> What about Cmd-Opt-H?
>
Cmd+Opt+H is also bound by the system for Hide Others.
2. Currently, items in the history menu open in the current foreground tab.
>> I'm currently working on a CL to make it so that if you hold down the Cmd
>> modif
cmd-opt-h is used by the os too (cmd-h: hide current app, cmd-opt-h:
hide others).
On Thu, Aug 13, 2009 at 8:08 AM, Julian Harris wrote:
> What about Cmd-Opt-H?
> On Wed, Aug 12, 2009 at 7:15 PM, Robert Sesek wrote:
>>
>> Two things about the Mac history menu that I'd like people to weigh in on:
What about Cmd-Opt-H?
On Wed, Aug 12, 2009 at 7:15 PM, Robert Sesek wrote:
> Two things about the Mac history menu that I'd like people to weigh in on:
> 1. The "Show All History" command should have a keyboard shortcut. We can't
> use the logical Cmd+H because it's bound by the system. Stuart su
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,
On Wed, Aug 12, 2009 at 2:18 PM, Robert Sesek wrote:
> On Wed, Aug 12, 2009 at 15:33, Scott Violet 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 WindowOp
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 wrote:
>
> The few times I've needed to use the history menu (gak
On Wed, Aug 12, 2009 at 15:33, Scott Violet 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 t
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
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 beli
Brett Wilson wrote:
> Windows always opens history in a new tab. I think this is the correct
> behavior: I don't think anybody expects going to history will clobber
> their current tab.
Not what was being talked about, as Avi pointed out, but does anyone
else find it annoying that going to histo
If there isn't already you should look into creating 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 th
On Wed, Aug 12, 2009 at 12:18 PM, Avi Drissman 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 f
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.
Avi
On Wed, Aug 12, 2009 at 3:14 PM, Brett W
On Wed, Aug 12, 2009 at 11:15 AM, Robert Sesek wrote:
> Two things about the Mac history menu that I'd like people to weigh in on:
> 1. The "Show All History" command should have a keyboard shortcut. We can't
> use the logical Cmd+H because it's bound by the system. Stuart suggested
> Cmd+Y, as th
I like firefox's approach with the recently closed in a submenu of the
history menu. Honestly though I can't say I use it very frequently. I
just feel safer knowing it's there.
-- Evan Stade
On Thu, May 28, 2009 at 1:14 PM, Ben Goodger (Google) wrote:
>
> I would say try as a replacement. i.e
I would say try as a replacement. i.e. similar to the dock menu... 9
most visited items + 3-4 recently closed
-Ben
On Thu, May 28, 2009 at 12:35 PM, Robert Sesek wrote:
> On Tue, May 26, 2009 at 00:59, Ben Goodger (Google)
> wrote:
>>
>> I think we had discussed adding most visited/recently cl
On Tue, May 26, 2009 at 00:59, Ben Goodger (Google) wrote:
> I think we had discussed adding most visited/recently closed items
> here, sort of like a NTP without the NTP.
>
I think this is an interesting idea, particularly the most recently closed
items. Are you thinking this is supplemental to
On Tue, May 26, 2009 at 12:59 AM, Ben Goodger (Google)
wrote:
> Wash your mouth out with soap. The availability of real estate is
> never an excuse to use it in Chrome :-P
Ok, we'll just go without because it doesn't exist in windows. :P
--
Mike Pinkerton
Mac Weenie
pinker...@google.com
--~-
Wash your mouth out with soap. The availability of real estate is
never an excuse to use it in Chrome :-P
I think we had discussed adding most visited/recently closed items
here, sort of like a NTP without the NTP.
-Ben
On Mon, May 25, 2009 at 7:43 AM, Mike Pinkerton wrote:
>
> Session history
Session history != global browser history. The back/forward buttons
don't get you anything outside of the current tab's session.
Amanda's point about fitts' law is another good one. The History menu
is an easy way to get to something you visited recently with one click
(vs. the alternative of ope
On Sat, May 23, 2009 at 12:22 AM, Mark Larson (Google)
wrote:
> Just so it's clear to me... why do we need a History menu?
> There's a link to history from the wrench menu/Ctrl+H and also from the New
> Tab page.
> The
> back button provides at least 12 entries from the back history for the cur
Just so it's clear to me... why do we need a History menu?
There's a link to history from the wrench menu/Ctrl+H and also from the New
Tab page.
The
back button provides at least 12 entries from the back history for the
current tab. That seems more than
adequate for the 'jump back a few steps in m
On Fri, May 22, 2009 at 7:22 PM, Robert Sesek wrote:
> I think that Firefox's implemntation makes the most sense from a
> usability perspective. Those long menus in Safari are next to
> worthless if you have a decent-sized browsing history and really just
> clutter things up. Camino's implemntati
27 matches
Mail list logo
