W3C home > Mailing lists > Public > public-css-archive@w3.org > November 2018

Re: [csswg-drafts] [css-selectors] Why does `:is()` have the specificity of the most specific selector in its arguments?

From: fantasai via GitHub <sysbot+gh@w3.org>
Date: Thu, 15 Nov 2018 21:44:37 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-439201206-1542318276-sysbot+gh@w3.org>

Closing out, please re-open if there's something to fix.

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

Received on Thursday, 15 November 2018 21:44:38 UTC

This message: [ Message body ]
Next message: Eric Willigers via GitHub: "Re: [csswg-drafts] [selectors-4] Rename :matches() to :is()"
Previous message: fantasai via GitHub: "Closed: [csswg-drafts] [css-selectors] Why does `:is()` have the specificity of the most specific selector in its arguments?"
In reply to: ExE Boss via GitHub: "[csswg-drafts] [css-selectors] Why does `:is()` have the specificity of the most specific selector in its arguments?"

Mail actions: [ respond to this message ] [ mail a new topic ]
Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]
Help: [ How to use the archives ] [ Search in the archives ]

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