Re: [csswg-drafts] [css-conditional] Should CSS.supports() accept !important in the 2nd argument? (#5692)

I personally think it should be as it is in Firefox /  Chromium. Meaning:

```
CSS.supports("background: green !important"); // true
CSS.supports("background", "green !important"); // false
```

It's similar to function overloading. As the arguments are different. 

At `CSS.supports(conditionText)` the `!important` is seen as part of the condition and the whole term is evaluated as condition. 

At `CSS.supports(property, value)` the `!important` has no real affiliation to neither of the two arguements. As in this case the two arguments are parsed separately and the value  **_parses according to that property’s grammar_**.

> * If `property` is an ASCII case-insensitive match for any defined CSS property that the UA supports, **and** `value` successfully parses according to that property’s grammar, return `true`.
> * Otherwise, if `property` is a custom property name string, return `true`.
> * Otherwise, return `false`.



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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 3 November 2020 23:55:11 UTC