Re: [csswg-drafts] [css-env-1] Should env() really use <custom-ident>?

Ah yeah, that's unfortunate. We exclude the global keywords with the assumption that most custom idents will be used top-level in a declaration, but function arguments don't have to obey that; they're already excluded from triggering the global behavior.

This is similar to [the distinction Syntax draws between `<declaration-value>` and `<any-value>`](https://drafts.csswg.org/css-syntax/#any-value); maybe that means we should define a less restrictive `<any-ident>` production that can be used when appropriate, that doesn't exclude anything by default?

-- 
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3262#issuecomment-434040759 using your GitHub account

Received on Monday, 29 October 2018 19:08:45 UTC