Closed
Bug 47351
(key-equivalent)
Opened 24 years ago
Closed 15 years ago
key-equivalent should support multiple values
Categories
(Core :: CSS Parsing and Computation, defect, P4)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
WONTFIX
Future
People
(Reporter: akkzilla, Unassigned)
References
()
Details
(Keywords: css3)
The CSS property for key-equivalent doesn't support multiple values (see the "XXX need to deal with multiple values" and "XXX To be implemented" comments in MapDeclarationUIInto in nsCSSStyleRule.cpp). We have numerous accelerators which require multiple modifier keys, e.g. control-shift-N to open a new editor window. Currently these are implemented using XUL bindings, so I believe we're not actually dependant on key-equivalent, but if we want key bindings to work without a XUL layer, we might need this. Cc'ing Kathy since she has at least one bug regarding handling of bindings with multiple modifier keys.
Comment 1•24 years ago
|
||
We need this for the UI, nominating for nsBeta3.
Comment 2•24 years ago
|
||
This is not a requirement for ship, is it? I think there's been some confusion here. (Maybe I'm the one that's confused.) AFAIK, this can safely be futured and is not needed for the UI.
Comment 3•24 years ago
|
||
I guess I'm the one who was wrong. Marking future. If you have really need that fixed, just say so.
Keywords: nsbeta3
Target Milestone: --- → Future
Reporter | ||
Comment 4•24 years ago
|
||
Future is fine. We're going to do the modifier key with a pref for now, and move it into CSS some other time.
Comment 5•24 years ago
|
||
Netscape's standard compliance QA team reorganised itself once again, so taking remaining non-tables style bugs. Sorry about the spam. I tried to get this done directly at the database level, but apparently that is "not easy because of the shadow db", "plus it screws up the audit trail", so no can do...
QA Contact: chrisd → ian
Priority: P3 → P4
Assigning pierre's remaining Style System-related bugs to myself.
Assignee: pierre → dbaron
Status: ASSIGNED → NEW
Updated•20 years ago
|
Comment 7•20 years ago
|
||
This property has been removed from CSS3 UI. Do we still need it?
Assignee: dbaron → nobody
QA Contact: ian → style-system
Implementation was removed in bug 265721, thus -> wontfix.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•