Bug 204506 - [css-grid] Serialization of custom identifiers
Summary: [css-grid] Serialization of custom identifiers
Status: RESOLVED DUPLICATE of bug 226694
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-22 03:56 PST by Manuel Rego Casasnovas
Modified: 2021-06-09 05:27 PDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Manuel Rego Casasnovas 2019-11-22 03:56:56 PST
Things like "\\31st" are not serialize like "\\31st" right now, this causes failures in http://w3c-test.org/css/css-grid/parsing/grid-area-computed.html (Blink and Firefox does this right).
This was discussed at https://github.com/w3c/csswg-drafts/issues/2858

Also grid-area: "--a" has similar problems, and http://w3c-test.org/css/css-grid/parsing/grid-area-shorthand.html also fails only in WebKit.

Not sure if it's exactly the same issue or 2 separated ones.
Comment 1 Carlos Alberto Lopez Perez 2020-03-30 11:53:43 PDT
(In reply to Manuel Rego Casasnovas from comment #0)
> Also grid-area: "--a" has similar problems, and
> http://w3c-test.org/css/css-grid/parsing/grid-area-shorthand.html also fails
> only in WebKit.
> 

I guess grid-area-shorthand also fails due to bug 204611
Comment 2 Oriol Brufau 2020-05-25 17:18:28 PDT
This seems to affect all properties that accept custom idents (animation-name is a non-grid example). Relevant comment:

    // FIXME-NEWPARSER: Eventually we'd like this to use CSSCustomIdentValue, but we need
    // to do other plumbing work first (like changing Pair to CSSValuePair and make it not
    // use only primitive values).
    RefPtr<CSSPrimitiveValue> consumeCustomIdent(CSSParserTokenRange& range)
Comment 3 zsun 2021-06-09 04:27:09 PDT
This has been fixed at -
https://bugs.webkit.org/show_bug.cgi?id=226694
Comment 4 Oriol Brufau 2021-06-09 05:27:09 PDT

*** This bug has been marked as a duplicate of bug 226694 ***