fix(css‑env): Fix env() function syntax definition - #3475
Closed
ExE-Boss wants to merge 1 commit into
Closed
Conversation
Member
|
No, commas are implicitly omittable if they're not separating anything. (This makes some grammars far easier to write, and simplifies the look of even simple grammars like these.) |
Member
|
(and they must be omitted in some cases listed in Tab's link, so your first example is explicitly not valid) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
https://drafts.csswg.org/css-env-1/#env-function
The current specification would require
prop: env(safe-area-inset-top,)to be valid andprop: env(safe-area-inset-top)to be invalid, but as we all know, it’s the other way around, so the spec is incorrect.See also:
env(…)function syntax mdn/data#326