Closed
Bug 433172
Opened 16 years ago
Closed 16 years ago
Don't report CSS style errors for values designated as vendor-specific
Categories
(Core :: CSS Parsing and Computation, enhancement)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
DUPLICATE
of bug 433074
People
(Reporter: davemgarrett, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9pre) Gecko/2008050918 Minefield/3.0pre
Build Identifier:
See bug 393757. Vendor-specific _identifiers_ are filtered out but not values. See bug 423564 for an example from Bugzilla.
Simple suggestion: Apply (a version of) the filter added in bug 393757 to CSS values too.
Might not be that simple, but some filter is needed.
Reproducible: Always
Comment 1•16 years ago
|
||
This is exactly the reason that bug 433074 exists, in my mind; I hadn't closed the bug that preceded it because we haven't done this yet.
As for simple, it's not. The problem is when parsing a property-value pair, we condition the parsing of the value on the name of the property, so there's no single point to change to just make this happen for every property. (I believe this is necessary, but there's probably some fuzz room to cut down on the problem in some cases -- it just hasn't been done since, all things considered, a CSS warning isn't that big a deal.) At the time I made the changes, we weren't interested in taking large/complicated patches, and the two changes made in the original bug were both small and simple -- this wouldn't be.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 2•16 years ago
|
||
Oh, sorry. You might want to rename that one to something a little more general then.
You need to log in
before you can comment on or make changes to this bug.
Description
•