incorrectly believing rules which contain a mix of the color() function and var() custom property references are supported
Reported by
gra...@foundersfactory.co,
Aug 22 2016
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36 Example URL: http://codepen.io/anon/pen/WxBRmK Steps to reproduce the problem: 1. Use future css color() syntax combined with custom property reference 2. add rule before with static color value (no css color() function or var() lookup) 3. observe that the future syntax rule is not being ignored by chrome (as it should be, since the syntax isn't supported yet) What is the expected behavior? chrome should ignore the newer style rule (until that syntax is supported) What went wrong? chrome incorrectly identifies a combination of color() and var() as valid syntax (actually, anything with var() in it) and attempts to use that rule, but can't. The fallback rule is therefore incorrectly ignored. Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? No Firefox 45.0.2 Chrome version: 51.0.2704.103 Channel: n/a OS Version: OS X 10.11.3 Flash Version: Shockwave Flash 22.0 r0
,
Aug 22 2016
This is working as intended (which is why other browsers behaves the same). Please see the specification: https://drafts.csswg.org/css-variables/
,
Aug 22 2016
you're right - I'd failed to appreciate the 'invalid at compute time' part of the spec. Sorry for the noise :) |
||
►
Sign in to add a comment |
||
Comment 1 by dtapu...@chromium.org
, Aug 22 2016