Open
Bug 1175753
Opened 11 years ago
Updated 3 years ago
hyphen should be tokenized as a delim if followed by an invalid escape
Categories
(Core :: CSS Parsing and Computation, defect)
Core
CSS Parsing and Computation
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox41 | --- | affected |
People
(Reporter: heycam, Unassigned)
Details
Attachments
(1 file)
|
280 bytes,
text/html
|
Details |
From bug 1175192 comment 4:
> The three character sequence "-\\\n" should tokenize as '-' delim,
> '\\' delim (and an error), "\n" white space. But I think we currently
> tokenize it as '-' ident, '\\' delim, "\n" white space.
>
> AFAICT the only place where a '\\' delim will not cause a parse error is in
> the value of a custom property. Because of the rules about inserting /**/
> between certain adjacent tokens when expanding out var() functions, whether
> the '-' (incorrectly) becomes an ident or (correctly) becomes a delim can
> determine whether that /**/ is generated.
>
> The attachment illustrates. I think the spec should require the computed
> value of --b to be serialized as "1-\\\nx", whereas we currently serialize
> it as "1/**/-\\\nx".
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•