Closed
Bug 1102650
Opened 11 years ago
Closed 11 years ago
Selectors with the pseudo class :(-moz-)dir() should be valid when the argument is a valid identifier
Categories
(Core :: CSS Parsing and Computation, defect)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
FIXED
mozilla36
People
(Reporter: benjamin, Assigned: dbaron)
Details
Attachments
(1 file)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/600.3.6 (KHTML, like Gecko) Version/8.0.2 Safari/600.3.6
Steps to reproduce:
See the following codepen: http://codepen.io/anon/pen/ZYYRrj
Actual results:
The text should be styled green.
Expected results:
The selector is considered invalid. It should be matching nothing instead (http://dev.w3.org/csswg/selectors4/#the-dir-pseudo).
Since it is considered invalid, the universal selector is ignored.
Kudos to Sukolsak Sakshuwong for catching the bug.
| Assignee | ||
Comment 1•11 years ago
|
||
Yeah, I don't see any rationale for why it was done the way our code does it.
| Assignee | ||
Comment 2•11 years ago
|
||
Attachment #8526592 -
Flags: review?(cam)
| Assignee | ||
Updated•11 years ago
|
Assignee: nobody → dbaron
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
| Assignee | ||
Updated•11 years ago
|
OS: Mac OS X → All
Hardware: x86 → All
Comment 3•11 years ago
|
||
Comment on attachment 8526592 [details] [diff] [review]
Make the :-moz-dir() and :-moz-locale-dir() selectors be valid selectors (matching nothing) with arguments other than rtl and ltr, rather than invalid
I assume it's OK that we serialize values other than "ltr" and "rtl" after converting them to lowercase?
Attachment #8526592 -
Flags: review?(cam) → review+
| Assignee | ||
Comment 4•11 years ago
|
||
I think so, given that CSS values are all case-insensitive, and the values likely to be added are things like tb-rl and tb-lr, or maybe ttb.
| Assignee | ||
Comment 5•11 years ago
|
||
Comment 6•11 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla36
You need to log in
before you can comment on or make changes to this bug.
Description
•