Closed Bug 55438 Opened 24 years ago Closed 24 years ago

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

Categories

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

defect

Tracking

()

VERIFIED DUPLICATE of bug 53667

People

(Reporter: mcafee, Assigned: mcafee)

Details

(Whiteboard: [rtm need info])

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
adding to rtm radar
Keywords: rtm
which of these accelerators still doesn't work?
There are two listed here, neither are working
Easily fixed, see platformNavigationBindings.xul. Does alt left/right work for either of you btw? Mine open Search and QA menus.
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...
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).
ok, alt+< doesn't work on Linux, works on w2k.
Summary: Ctrl + Arrow key {left|right} = {back|forward} → Modifier Key + Arrow key {left|right} = {back|forward}
I like the BackSpace for back like in Explorer (and IE).
If this is a regression, when did it break? Chris, is there a patch to fix this yet?
Priority: P3 → P2
Whiteboard: [rtm need info]
Eugene, on windows, backspace and shift-backspace do navigate back and forward respectively.
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.
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?
Ohh... But for what does shift-backspace?
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.
dup of 53667 *** This bug has been marked as a duplicate of 53667 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
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.
reopen is fine with me, please differentiate this bug with the dup bug.
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.
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?
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...
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.
Status: RESOLVED → VERIFIED
Component: Keyboard: Navigation → User events and focus handling
You need to log in before you can comment on or make changes to this bug.