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)

defect

Tracking

()

Tracking Status
firefox57 --- wontfix
firefox58 --- wontfix
firefox59 --- ?

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.
Priority: -- → P3
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)
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)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.