Closed
Bug 11817
Opened 25 years ago
Closed 25 years ago
key binding code should assume false for modifier keys
Categories
(Core :: XUL, defect, P3)
Tracking
()
VERIFIED
FIXED
M10
People
(Reporter: akkzilla, Assigned: saari)
References
Details
(Whiteboard: Easy to fix, but irrelevant compared to other issues to be decided on Tues.)
Hyatt says that XUL key bindings are supposed to assume false for any modifier not specified in the XUL, instead of having to specify things like shift="false" for every modifier. That isn't the way they work now -- currently, if a modifier is unspecified in the xul, then both set and unset for that modifier will match. This might also simplify the "special command key" handling code.
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M10
Assignee | ||
Comment 1•25 years ago
|
||
targeting early M10
Assignee | ||
Updated•25 years ago
|
Whiteboard: Easy to fix, but irrelevant compared to other issues to be decided on Tues.
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 2•25 years ago
|
||
Fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•