If space-bar is like a button click then it should access navigation history menu from back/forward nav buttons |
||
Issue descriptionVersion: 53.0.2750.0 (maybe others) OS: Windows 8.1 & 10 What steps will reproduce the problem? (1) Browse until there are several entries in the history (2) Shift-Alt-T to focus the back nav button on the toolbar (3) Press and hold the space-bar EXPECTED: After .5 (or whatever the mouse button down delay is) second delay, the browser history menu should drop down ACTUAL: Nothing happens. ---- NOTE: Pressing the dedicating local menu key on Windows specific keyboards *will* invoke the menu. Not all keyboards have this key.
,
Jun 28 2016
Cannot get the drop-down to show on down-arrow. This is Windows; maybe this works on Linux? Either way, that doesn't negate the behavior I expect. Pressing the space-bar on any button in Windows should be the same as a mouse-click. Likewise, a press-and-hold with the space-bar should also behave the same.
,
Jun 29 2016
True, the difference between acting on press or release for either spacebar or the mouse button is mostly incidental and probably does not merit messing with. The back/forward/reload buttons have a secondary action that currently can only be triggered with the mouse (press and hold, or right-click), or with a somewhat obscure keyboard shortcut (menu key / shift+F10) (this is on Windows). I think adding an easy way to access this secondary action with the keyboard would be a good thing. Long-pressing the spacebar would probably not be the right approach, but I think the down arrow key would parallel the other buttons in the toolbar (extension buttons and the menu button), and would therefore be easy to discover.
,
Jun 29 2016
I don't really agree that the action is incidental. It's highly volitional. IOW, why click or press the space-bar if the action behind it just happens to happen? I'm also looking at this from an accessibility angle as well. Requiring some other action in order to invoke that menu may be OK in some instances, for many folks that may not be an option. At the very least, having another way to invoke that action could help extend usability to other groups. The long-click and it's relative, the long-press (on touch systems), are relatively new concepts. While the keyboard seems to be somewhat passé these days, it is still one of the most productive input devices available. Extending these new concepts to the oldest form of input makes some sense.
,
Jun 30 2016
IMO whatever we decide to do should be a consistent system wide and not specific to the Back/Forward navigation buttons. I assume accessibility folks should own this and spec it out with UX? WDYT dmazzoni@ ?
,
Jun 30 2016
I only focused on the back/forward buttons because they are the obvious places where a long-click/long-press invokes a menu. Of course anyplace where a long-click/press invokes some alternative action, this should be considered.
,
Jan 10
Archiving P3s older than 1 year with no owner or component. |
||
►
Sign in to add a comment |
||
Comment 1 by jleedev@gmail.com
, Jun 28 2016