Showing content from https://www.w3.org/Style/CSS/Tracker/issues/318 below:
ISSUE-318: Make specificity of :matches() / :not() depend on what was matched
ISSUE-318: Make specificity of :matches() / :not() depend on what was matched Make specificity of :matches() / :not() depend on what was matched
-
State:
-
RAISED
-
Product:
-
Selectors Level 4
-
Raised by:
-
David Baron
-
Opened on:
-
2013-04-04
-
Description:
-
:matches() should be syntactic sugar for the writing-out of all possible combinations, so its specificity should be that of the most specific match. :not() should behave accordingly.
http://lists.w3.org/Archives/Public/www-style/2010Sep/0534.html
-
Related Actions Items:
-
No related actions
-
Related emails:
-
- Re: [selectors4] Open issues (from fantasai.lists@inkedblade.net on 2013-04-17)
- Re: [selectors4] Open issues (from peter.moulder@monash.edu on 2013-04-11)
- [CSSWG] Minutes Telecon 2013-04-10 (from fantasai.lists@inkedblade.net on 2013-04-10)
- Re: [selectors4] Open issues (from simon.sapin@exyr.org on 2013-04-09)
- [selectors4] Open issues (from fantasai.lists@inkedblade.net on 2013-04-08)
- CSS-ISSUE-318: Make specificity of :matches() / :not() depend on what was matched [Selectors Level 4] (from sysbot+tracker@w3.org on 2013-04-04)
Related notes:
No additional notes.
Display change log
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4