Skip to content

[css-properties-values-api] Require <custom-ident> as component name.#884

Merged
tabatkins merged 3 commits into
w3c:masterfrom
andruud:issue879
May 7, 2019
Merged

[css-properties-values-api] Require <custom-ident> as component name.#884
tabatkins merged 3 commits into
w3c:masterfrom
andruud:issue879

Conversation

@andruud
Copy link
Copy Markdown
Member

@andruud andruud commented May 6, 2019

Something like this was in the original syntax parsing PR, but it got
lost at some point.

Resolves #879.

Something like this was in the original syntax parsing PR, but it got
lost at some point.

Resolves w3c#879.
@andruud
Copy link
Copy Markdown
Member Author

andruud commented May 6, 2019

cc @tabatkins @emilio

@andruud
Copy link
Copy Markdown
Member Author

andruud commented May 6, 2019

Uhm, oops, that doesn't work, hold on.

@andruud
Copy link
Copy Markdown
Member Author

andruud commented May 6, 2019

There we go.

Copy link
Copy Markdown
Member

@tabatkins tabatkins left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can't match strings against productions, have to do a parse on it to turn it into a CSS value.

Comment thread css-properties-values-api/Overview.bs Outdated
Co-Authored-By: andruud <andruud@gmail.com>
@tabatkins tabatkins merged commit b4a12da into w3c:master May 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[css-properties-values-api] Consume a component name presumably shouldn't allow CSS wide keywords, but it does.

2 participants