Skip to content

[css-properties-values-api] The fact that "foo bar" and "foo | bar" are equivalent syntax is confusing. #893

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
emilio opened this issue May 29, 2019 · 2 comments · Fixed by #894

Comments

@emilio
Copy link
Contributor

emilio commented May 29, 2019

In https://drafts.css-houdini.org/css-properties-values-api-1/#consume-syntax-descriptor, | and any other character are treated basically equivalently, so it means that <length> <percentage> is really a syntax for <length> | <percentage>, rather than a <length>, then a <percentage>.

Is this intentional? Is there any reason we're closing the gate to more expressive syntaxes that allow multiple keywords?

@emilio
Copy link
Contributor Author

emilio commented May 29, 2019

cc @andruud

@andruud
Copy link
Member

andruud commented May 29, 2019

Yes, I just discovered this too. This is a mistake. "foo bar" etc is not supposed to work (and if it did, it certainly shouldn't work like that).

emilio added a commit to emilio/css-typed-om-syntax that referenced this issue May 29, 2019
This intentionally deviates from the spec, see w3c/css-houdini-drafts#893
emilio added a commit to emilio/css-houdini-drafts that referenced this issue May 29, 2019
…itespace between components the same as pipes.

Fixes w3c#893
emilio added a commit to emilio/css-houdini-drafts that referenced this issue May 30, 2019
…itespace between components the same as pipes.

Fixes w3c#893
emilio added a commit to emilio/css-houdini-drafts that referenced this issue May 31, 2019
…itespace between components the same as pipes.

Fixes w3c#893
tabatkins pushed a commit that referenced this issue May 31, 2019
…itespace between components the same as pipes. (#894)

Fixes #893
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants