Closed
Bug 12398
Opened 25 years ago
Closed 24 years ago
attribute selector parsing regression
Categories
(Core :: CSS Parsing and Computation, defect, P3)
Core
CSS Parsing and Computation
Tracking
()
VERIFIED
FIXED
M16
People
(Reporter: dbaron, Assigned: dbaron)
References
()
Details
(Keywords: css2, Whiteboard: fix in hand)
Attachments
(2 files)
362 bytes,
text/html
|
Details | |
3.70 KB,
patch
|
Details | Diff | Splinter Review |
DESCRIPTION: I think (although I'm not sure) that this is a regression due to introduction of CSS3 namespace support. You do not parse the following correctly: [lang|="en"] However, this works: [lang |="en"] STEPS TO REPRODUCE: Load the attached test case. ACTUAL RESULTS: First line is green. Second is black. EXPECTED RESULTS: Second line should instead be blue. DOES NOT WORK CORRECTLY ON: * Linux, apprunner, 1999-08-20-13-M10 * Linux, viewer, 1999-06-11-08 WORKS CORRECTLY ON: * Linux, viewer, 1999-06-01-13 ADDITIONAL INFORMATION: I don't think this is a problem with the current namespaces draft, but you might want to check.
Assignee | ||
Comment 1•25 years ago
|
||
Assignee | ||
Comment 2•25 years ago
|
||
ALSO DOES NOT WORK CORRECTLY ON: * Windows, apprunner, 1999-08-24-09-M10
Comment 3•25 years ago
|
||
Moving non-beta 1 items to M15
Updated•25 years ago
|
Summary: attribute selector parsing regression → {css2} attribute selector parsing regression
Comment 4•25 years ago
|
||
Reassigning peterl's bugs to myself.
Comment 5•25 years ago
|
||
Accepting peterl's bugs that have a Target Milestone
Comment 6•25 years ago
|
||
Pushing my M15 bugs to M16
Comment 7•25 years ago
|
||
Migrating from {css2} to css2 keyword. The {css1}, {css2}, {css3} and {css-moz} radars should now be considered deprecated in favour of keywords. I am *really* sorry about the spam...
Updated•25 years ago
|
Summary: {css2} attribute selector parsing regression → attribute selector parsing regression
Assignee | ||
Comment 8•24 years ago
|
||
I took a look at this bug, and I found what seems to be a fix for it. It's an ugly fix, but I don't see an elegant way to do this. (See http://lists.w3.org/Archives/Public/www-style/2000Apr/0048.html for the problem.) I haven't tested the fix much yet. Would you want to use a patch this ugly?
Assignee | ||
Comment 9•24 years ago
|
||
Assignee | ||
Comment 10•24 years ago
|
||
Technically, the CSS grammar handles this by having separate tokens for ~= and |= . That would be a much cleaner fix, although it might be a little more work (though perhaps not). I'll have a look...
Assignee | ||
Comment 11•24 years ago
|
||
I have a much cleaner fix for this bug (changes the tokenization instead). Stealing bug.
Assignee: pierre → dbaron
Status: ASSIGNED → NEW
Assignee | ||
Updated•24 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 13•24 years ago
|
||
Fix checked in 2000-04-26 17:12 PDT.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Comment 14•24 years ago
|
||
Marking VERIFIED FIXED on: - MacOS9 2000-07-06-08-M17 Commercial - Linux6 2000-07-09-20-M17 Commercial - Win98 2000-07-09-21-M17 Commercial
Status: RESOLVED → VERIFIED
Comment hidden (collapsed) |
You need to log in
before you can comment on or make changes to this bug.
Description
•