Note: There are a few cases of duplicates in user autocompletion which are being worked on.

add conditional testing for accesskey conflicts in release binaries

RESOLVED WONTFIX

Status

()

Core
Keyboard: Navigation
RESOLVED WONTFIX
11 years ago
11 years ago

People

(Reporter: Pike, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

11 years ago
It would be good to have the testing code for accesskey conflicts in release code so that localization teams and tests could check for that in release software or tinderbox configs.

It should probably the same code that is current DEBUG_jag and protected by a pref.
(Reporter)

Comment 1

11 years ago
Actually, the most important part would be accesskeys in menus, and that's a tad tougher, and doesn't go through nsEventStateManager.cpp, but through layout in 
http://lxr.mozilla.org/mozilla/source/layout/xul/base/src/nsMenuPopupFrame.cpp#1521.

The rest is not really worth it, so I'm WONTFIXing this one.
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.