-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Selectors #31
Comments
So, one by one:
This should be trivial to calculate with parsel.
Same as above.
Nice. Let's track this in #5.
Nice one. How would you define "longest"? Highest number of compound selectors in a complex selector? Highest number of simple selectors?
Do you count selector lists as one or multiple selectors? I.e. are you asking about the number of rules, or about the number of complex selectors?
This is computed in #6.
This is (msostly) computed in #6 and #9 .
This is computed in #6, but we should keep track of this as something to look for in the results. |
This was also measured in #5 so we should avoid re-measuring it here. So basically, to sum up what we actually need to calculate here that's not measured by any other stats:
|
Assuming "most common" should be interpreted as the name occurring on the most pages, not the name used the most number of times per page. LMK if anyone had a different idea in mind. |
@LeaVerou is there JS for combinators? Not seeing support for it in https://github.com/LeaVerou/css-almanac/blob/master/js/31-selector-parts.js |
I think both strategies are reasonable, either weighing things higher if they appear more times on average, or not doing so. We could even follow a hybrid strategy of having "buckets" of weights, but that's more complicated to code and to explain.
I didn't account for it, as I didn't think it was that interesting but if we think it's needed, I can easily add it. |
Replicated everything from last year:
[attr]
, exact([attr=val]
), starts with ([attr^=val]
), ends with([attr$=val]
), substring([attr*=val]
), language([attr|=val]
). Used at all; not just in relation to ID or classAdd some features:
>
,+
, and~
, as well as:not
(maybe we should leave space out)::before
(incl:before
),::after
,::first-letter
,::first-line
,::selection
(incl prefixed)::-webkit-X
,::-ms-X
, and::-moz-
like::-webkit-inner-spin-button
are people including, including non-prefixed, such as::file-chooser-button
.:checked
,:valid
, etc.The text was updated successfully, but these errors were encountered: