Open
Bug 1378858
Opened 7 years ago
Updated 2 years ago
rust-cssparser treats quoted URLs as a "url" function followed by a string
Categories
(Core :: CSS Parsing and Computation, defect, P3)
Core
CSS Parsing and Computation
Tracking
()
NEW
People
(Reporter: jdm, Unassigned)
References
(Blocks 1 open bug)
Details
rust-cssparser is modeled after a more recent change to the CSS parsing specification. It's generally black-box compatible with the previous representation that Gecko's parser follows (a single URL token that indicates whether it's quoted or not), but it does affect the error reporting capabilities of the parser for invalid quoted URLs. test_parser_diagnostics_unprintables.html explicitly checks some cases where Stylo's parsing is unable to report the actual invalid string value the same way that Gecko can.
Updated•7 years ago
|
Priority: -- → P3
Comment 1•7 years ago
|
||
jdm, could you clarify what the real-world impact of this is? (Is it only absence/presence of quotes in error reports in the browser console?) And, should this block shipping 57/stylo?
Flags: needinfo?(josh)
Reporter | ||
Comment 2•7 years ago
|
||
The real world impact is that erroneous CSS like `x { url('foo') }` reports slightly less informative error messages under Stylo than Gecko. Gecko: Expected declaraction but found `url('foo')`. Stylo: Expected declaration but found `url(`. This should not block shipping.
Flags: needinfo?(josh)
Updated•7 years ago
|
status-firefox57:
--- → wontfix
status-firefox58:
--- → fix-optional
Comment 3•6 years ago
|
||
https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Move_fix-optionals
status-firefox59:
--- → ?
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•