We're not renaming `:matches()`; it's already shipped in Safari and I think Firefox and Chrome are soon to ship? I'm still okay with just adding the functionality to `:matches()`, with the default being the current "specificity of the most specific branch that matched". If we do make a separate function, I'm still happy with `:is()`; the possibility for confusion is there, but oh well. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2143#issuecomment-354888225 using your GitHub accountReceived on Tuesday, 2 January 2018 22:08:14 UTC
This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:22 UTC