Closed Bug 330400 Opened 18 years ago Closed 18 years ago

site accesskeys conflict with emacs keybindings

Categories

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

PowerPC
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 303192

People

(Reporter: solushex, Assigned: aaronlev)

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1

there still appears to be no satisfactory way to reconcile the conflict between accesskeys and emacs keys on the mac.

1. by default, accesskeys override emacs keys in textfields.
2. changing ui.key.generalAccessKey doesn't work properly, since:
--a. the only free modifier left is (alt), and that keycode is broken (see the six-year-old bug 44259).
--b. ctrl-alt works instead, but aside from its awkwardess, it overwrites textfield default input (try it on this page).
3. disabling accesskeys altogether isn't a satisfactory solution.

Reproducible: Always




1. resolving bug 44259 would be great, but it doesn't seem to be getting anywhere.  
2. i remember reading some bug report requesting additional accesskey modifiers, but i can't find it now.
3. a third possibility is to (optionally) disable accesskeys when focus is in textfields.
Related to bug 303192, bug 179816 and/or bug 128452?
(In reply to comment #1)
> Related to bug 303192, bug 179816 and/or bug 128452?
> 

but 179816 was the one i couldn't find, but i'd like something other than (shift) for the modifier.  bug 128452 seems to have dead-ended with the solution of disabling accesskeys, which i don't consider "satisfactory."

i never noticed bug 303192 before (thanks for the reference).  hopefully it'll lead somewhere.

*** This bug has been marked as a duplicate of 303192 ***
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
Component: Keyboard: Navigation → User events and focus handling
You need to log in before you can comment on or make changes to this bug.