- From: Ilya Streltsyn via GitHub <sysbot+gh@w3.org>
- Date: Mon, 29 Oct 2018 09:41:32 +0000
- To: public-css-archive@w3.org
I agree that, since the WebKit's implementation of `:matches()` is now not conforming to the changed spec, it would be better to drop `:matches()` at all (like `:any()`) and rename this functionality with the improved specificity rules to `:is()`. But I suppose that after such a change there should be a signal for the vendors that _this time_ the new definition of `:is()` is _really_ stable and it's safe to implement it. Maybe it's time to defer the less stable Selector features (like `:has()` and Live/Snapshot "profiles") to Level 5 and make the rest of Level 4 features transition to CR as fast as possible? Also, is the current implementation of `:nth-*-child(... of S)` in WebKit conforming to the current spec? Doesn't it currently have the same problem as the implementation of `:matches()`? -- GitHub Notification of comment by SelenIT Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3258#issuecomment-433845931 using your GitHub account
Received on Monday, 29 October 2018 09:41:32 UTC