Open
Bug 433074
Opened 16 years ago
Updated 2 years ago
Don't report errors for vendor-specific CSS property values (start with _, or - but not -moz-)
Categories
(Core :: CSS Parsing and Computation, defect)
Core
CSS Parsing and Computation
Tracking
()
NEW
People
(Reporter: dbaron, Unassigned)
References
Details
This is followup for bug 393757. I think the main thing remaining in that bug was not to report errors for identifiers starting with mso-, but there might have been others that I missed.
Comment 1•16 years ago
|
||
I was hoping not to do the mso- ones since the spec doesn't carve out an exception for them. What's missing is not reporting errors for property values -- there's no central flow point for parsing an arbitrary property, so the only option I saw was hacking every property, which seemed ridiculously error-prone. I *think* that was the only thing remaining.
Comment 2•16 years ago
|
||
Another followup: Vendor-specific values need to be filtered too. See bug 433172.
Updated•16 years ago
|
Summary: don't report errors for identifiers starting with mso- → Don't report errors for vendor-specific CSS property values (start with _, or - but not -moz-)
Comment 4•16 years ago
|
||
Note that fixing this bug, especially comment 1, would fix bug 423564. Jeff, is that something you plan to fix?
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•