rust-cssparser treats quoted URLs as a "url" function followed by a string

NEW
Unassigned

Status

()

P3
normal
a year ago
10 months ago

People

(Reporter: jdm, Unassigned)

Tracking

(Blocks: 1 bug)

unspecified
Points:
---

Firefox Tracking Flags

(firefox57 wontfix, firefox58 wontfix, firefox59 ?)

Details

(Reporter)

Description

a year ago
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)
(Reporter)

Comment 2

a year 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)
status-firefox57: --- → wontfix
status-firefox58: --- → fix-optional
You need to log in before you can comment on or make changes to this bug.