Closed
Bug 83616
Opened 23 years ago
Closed 23 years ago
:not(.foo) broken
Categories
(Core :: CSS Parsing and Computation, defect, P2)
Core
CSS Parsing and Computation
Tracking
()
VERIFIED
FIXED
mozilla0.9.2
People
(Reporter: dbaron, Assigned: dbaron)
References
Details
(Keywords: css3, testcase, Whiteboard: [Hixie-P4])
Attachments
(3 files)
(deleted),
text/html
|
Details | |
(deleted),
patch
|
Details | Diff | Splinter Review | |
(deleted),
patch
|
Details | Diff | Splinter Review |
:not(.foo) (i.e., :not() with a class selector inside) is broken. The problem
can be fixed by changing 2 adjacent lines in nsCSSStyleSheet.cpp. It's caused
by using the "local" boolean in the wrong place.
Testcase to be attached.
Assignee | ||
Comment 1•23 years ago
|
||
Comment 2•23 years ago
|
||
Updated•23 years ago
|
Priority: -- → P3
Target Milestone: --- → mozilla1.0
Assignee | ||
Comment 3•23 years ago
|
||
Assignee | ||
Updated•23 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Updated•23 years ago
|
Priority: P3 → P2
Target Milestone: mozilla1.0 → mozilla0.9.2
Comment 5•23 years ago
|
||
Looks fine. [s]r=attinasi - thanks David.
Comment 6•23 years ago
|
||
per discussion on IRC, r=hixie
Assignee | ||
Comment 7•23 years ago
|
||
Assignee | ||
Comment 8•23 years ago
|
||
OK, I'm happy with the correctness of the changes in the above patch (did a bit
of local testing with a single element and single selector that I kept
changing), and they do fix the bugs I expected them to fix.
I think we should get the WG to clarify the meaning of |= though, since I don't
think Daniel's interpretation is backed by the spec.
Comment 10•23 years ago
|
||
sr=attinasi on the latest patch.
Comment 11•23 years ago
|
||
r=hixie
New test case: http://hixie.ch/tests/adhoc/css/selectors/not/010.xml
Comment 12•23 years ago
|
||
a= asa@mozilla.org for checkin to the trunk.
(on behalf of drivers)
Blocks: 83989
Assignee | ||
Comment 13•23 years ago
|
||
Fix checked in 2001-06-19 15:46 PDT.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•