W3C home > Mailing lists > Public > public-css-archive@w3.org > February 2017

[csswg-drafts] [css-conditional] Unbalanced brackets in @supports condition

From: Xidorn Quan via GitHub <sysbot+gh@w3.org>
Date: Fri, 10 Feb 2017 03:18:11 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-206697399-1486696690-sysbot+gh@w3.org>
upsuper has just created a new issue for 

== [css-conditional] Unbalanced brackets in @supports condition ==
Gecko and Edge seem to reject (return false for `CSS.supports`) a 
condition if there is any unbalanced bracket, while Blink seems to 
accept it.

e.g. There are two conditions in Gecko's test suite:
* `not ({ something @with (unbalanced brackets })`
* `(color: green) or an-extension(that is [unbalanced)`

Gecko and Edge return `false` for both, while Blink returns `true` for

The spec doesn't seem to have anything about this. The question is, 
should it allow or disallow unbalanced brackets? Either way, it should
 probably be stated explicitly in the spec.

Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/1016 using your GitHub 
Received on Friday, 10 February 2017 03:18:18 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:08 UTC