- From: François REMY via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Sep 2017 17:29:34 +0000
- To: public-css-archive@w3.org
> 👍 for :is() as a pendent to :not() on the same specificity level - so the authors have the freedom to respect strict specificity But... isn't that exactly what `:matches` already does? I would rather have `:is` or `:when` be the name of the current `:filter` proposal. Maybe if you could clarify to me what the difference would be between :not(:not(x)) and :matches(x), then I would reconsider. Actually, the more I think about it, the more `button:when(:hover)` really appeals to me. Just look at it: `input:when([disabled])`. Isn't that wonderful? ^_^ -- GitHub Notification of comment by FremyCompany Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1170#issuecomment-330613109 using your GitHub account
Received on Tuesday, 19 September 2017 17:29:28 UTC