55438 - Modifier Key + Arrow key {left|right} = {back|forward}

Status: VERIFIED DUPLICATE of bug 53667

(Core :: DOM: UI Events & Focus Handling, defect, P2)

Description

[Chris McAfee]

from http://bugzilla.mozilla.org/show_bug.cgi?id=51597,
Add two acclerators for bac, forward:

Alt - Alt on Windows and Linux, Option on MacOS (unless stated otherwise)
Ctrl - Ctrl on Windows and Linux, Cmd on MacOS (unless stated otherwise)

Ctrl + Arrow Key Left    Back
Ctrl + Arrow Key Right   Forward

Comment 1

[Chris McAfee]

adding to rtm radar

Comment 2

[Blake Ross]

which of these accelerators still doesn't work?

Comment 3

[Chris McAfee]

There are two listed here, neither are working

Comment 4

[Peter "jag" Annema]

Easily fixed, see platformNavigationBindings.xul.

Does alt left/right work for either of you btw? Mine open Search and QA menus.

Comment 5

[Blake Ross]

alt+left|right arrow works for me on windows, with the noted caveat that the 
accelerator isn't listed in the menu, which is a separate bug...

Comment 6

[Chris McAfee]

dup of http://bugzilla.mozilla.org/show_bug.cgi?id=53667 ?

Comment 7

[Matthew T (active 1999-2002)]

Wontfix! Ctrl+Left/Right should go to the previous/next word (as it does in every 
other app), not the previous/next document.

Appropriate accelerators for Back and Forward are:
* Alt+Left/Right (Windows, X)
* Control+Left/Right (Mac OS)
* Command+Left/Right (Mac OS, 4xp, deprecated because of i18n problems).

Comment 8

[Chris McAfee]

ok, alt+< doesn't work on Linux, works on w2k.

Comment 9

[Eugene Savitsky]

I like the BackSpace for back like in Explorer (and IE).

Comment 10

[don]

If this is a regression, when did it break?

Chris, is there a patch to fix this yet?

Comment 11

[Peter "jag" Annema]

Eugene, on windows, backspace and shift-backspace do navigate back and forward
respectively.

Comment 12

[Peter "jag" Annema]

This appears to have regressed between 2000-09-19-08-M18 and 2000-09-19-21-M18. 

I suspect this has to do with the GTK key handling fixes akkana checked in
around that time, except she's not seeing any of this. cc'ing her.

Comment 13

[Peter "jag" Annema]

Btw, shouldn't the latter part of this discussion be in bug 53667?

This bug is about making accel + arrows (or is that specifically ctrl + arrows?)
work for back/forward navigation.

mpt: ctrl-left/right can do back/forward a word while an editing widget has
focus, and navigate back/forward when the browser has focus. Or would that be
bad ui?

Comment 14

[Eugene Savitsky]

Ohh... But for what does shift-backspace? 

Comment 15

[Matthew T (active 1999-2002)]

jag: making Ctrl+Left/+Right modal in that way would be exceptionally bad UI -- 
for example, you might be trying to use the shortcuts to flip through several 
pages one of which uses a script to put focus in a text field. Ctrl+Left/+Right 
should always just do word navigation, and Alt+Left/+Right should always just 
do document navigation.

Comment 16

[Chris McAfee]

dup of 53667


*** This bug has been marked as a duplicate of 53667 ***

Comment 17

[Peter "jag" Annema]

McAfee, would you mind if we keep this bug open as a tracker for accel +
left/right? Or is there an agreement on using alt + left/right instead?

The bug you marked this a dupe on is specifically about making alt + left/right
work again after it was broken in GtkEventHandler code a few weeks ago.

Comment 18

[Chris McAfee]

reopen is fine with me, please differentiate this bug with the dup bug.

Comment 19

[Ben Bucksch (:BenB)]

Note that is it also a dup of bug 55759, which is still open and has more
discussion. So, I suggest to leave the closed and fix bug 55759.

Comment 20

[Peter "jag" Annema]

Sounds good to me... What are the specs on this all, btw? I recall them
specifying ctrl left/right, has that changed or is it still the same?

Comment 21

[sairuh (rarely reading bugmail)]

jag, the accelerator spec is at
http://mozilla.org/projects/ui/netscape/accel_keys/index.html --however, jglick
has a more recent version which i shall be checking in soon...

Comment 22

[sairuh (rarely reading bugmail)]

mass verification of duplicate bugs: to find all bugspam pertaining to this, set
your search string to "DuplicateBugsBelongInZahadum".

if you think this particular bug is *not* a duplicate, please provide a
compelling reason, as well as check a recent *trunk* build (on the appropriate
platform[s]), before reopening.