New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 921152 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

CSS.supports / @supports doesn't consider valid any value with custom property references / env.

Project Member Reported by emilio@chromium.org, Jan 11

Issue description

Chrome Version       : Trunk
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari: PASS
    Firefox: PASS
    IE/Edge: didn't check

What steps will reproduce the problem?
1. Run on the console CSS.supports("margin: var(--foo) something absolutely pointless")
2. Run on the console CSS.supports("margin: someting-absolutely-pointless(var(--foo))")

What is the expected result?
Both return true, parse, and compute to invalid at computed-value time.

What happens instead of that?
First one correctly returns true, but second one does not. But I don't see what should make them behave differently.
 
Status: Available (was: Unconfirmed)
Confirmed that both should be valid at parse time; the mere *presence* of a var() function in the tokens of a property automatically switch it to "assumed valid at parse time, check it after substitution" behavior.

Source: I wrote the spec.

Sign in to add a comment