GITHUB . COM {}

Detected CMS Systems:

Wordpress (2 occurrences)

Analyzed Page
Matching Content Categories
CMS
Monthly Traffic Estimate
How Does Github.com Make Money
How Much Does Github.com Make
Wordpress Themes And Plugins
Keywords
Topics
Payment Methods
Questions
Schema
External Links
Analytics And Tracking
Libraries
Hosting Providers

We are analyzing https://github.com/w3c/csswg-drafts/issues/8122.

Title:
[selectors-4] Legacy `:` pseudo-element cannot appear before type/subclass selectors · Issue #8122 · w3c/csswg-drafts
Description:
Chrome/FF seems to parse :before#id or :before.class as invalid (instead of valid and matching nothing) but I do not see on which part of the spec this is based. Pseudo-elements are featureless, and so can’t be matched by any other selec...
Website Age:
17 years and 8 months (reg. 2007-10-09).

Matching Content Categories {📚}

Non-Profit & Charity
Technology & Computing
Careers

Content Management System {📝}

What CMS is github.com built with?

Github.com employs WORDPRESS.

Traffic Estimate {📈}

What is the average monthly size of github.com audience?

🚀🌠 Tremendous Traffic: 10M - 20M visitors per month

Based on our best estimate, this website will receive around 10,000,019 visitors per month in the current month.
However, some sources were not loaded, we suggest to reload the page to get complete results.

check SE Ranking
check Ahrefs
check Similarweb
check Ubersuggest
check Semrush

How Does Github.com Make Money? {💸}

Subscription Packages {💳}

We've located a dedicated page on github.com that might include details about subscription plans or recurring payments. We identified it based on the word pricing in one of its internal links. Below, you'll find additional estimates for its monthly recurring revenues.

How Much Does Github.com Make? {💰}

Subscription Packages {💳}

Prices on github.com are in US Dollars ($). They range from $4.00/month to $21.00/month.
We estimate that the site has approximately 4,989,889 paying customers.
The estimated monthly recurring revenue (MRR) is $20,957,532.
The estimated annual recurring revenues (ARR) are $251,490,385.

Wordpress Themes and Plugins {🎨}

What WordPress theme does this site use?

It is strange but we were not able to detect any theme on the page.

What WordPress plugins does this website use?

It is strange but we were not able to detect any plugins on the page.

Keywords {🔍}

selectors, tabatkins, legacy, pseudoelement, commenter, issue, syntax, grammar, sign, closed, added, projects, cdoublev, pseudoelements, single, color, commented, satisfied, navigation, pull, requests, actions, security, typesubclass, invalid, spec, matched, subclassselector, pseudoclassselector, pseudoelementselector, stops, member, commit, references, move, current, work, accepted, editorial, response, pending, satisfaction, resolution, edits, github, type, milestone, footer, skip, content,

Topics {✒️}

legacy pseudo-element syntax pseudo-element syntax tabatkins added tabatkins closed subclass selectors similar confusion occurred comment metadata assignees level 2 pseudo-elements type projects pseudo-element ` pseudo-element projects milestone legacy reasons pseudo-elements legacy single syntax requires selector class color stops additional rule custom validation resolution / edits milestone relationships legacy single colon github satisfied grammar accepts syntax matched color elements single stops grammar skip jump sign parse invalid valid matching part spec based featureless make defined order selecting

Payment Methods {📊}

Braintree

Questions {❓}

= [ ?
Already have an account?

Schema {🗺️}

DiscussionForumPosting:
      context:https://schema.org
      headline:[selectors-4] Legacy `:` pseudo-element cannot appear before type/subclass selectors
      articleBody:Chrome/FF seems to parse `:before#id` or `:before.class` as invalid (instead of valid and matching nothing) but I do not see on which part of the spec this is based. > *Pseudo-elements are featureless, and so can’t be matched by any other selector* This does not make them invalid. Legacy `:` pseudo-element syntax is defined in `<subclass-selector>` as a `<pseudo-class-selector>`. > `<compound-selector> = [ <type-selector>? <subclass-selector>* [ <pseudo-element-selector> <pseudo-class-selector>* ]* ]!` Subclass selectors can appear in any order while still selecting the same set of elements, but this is not true for a pseudo-element specified with the legacy single `:` syntax. Therefore I assume that `:before` must be handled as if it has been specified with `::before` and matched `<pseudo-element-selector>`. **If so, it may be helpfull to define it in the spec.** A [similar confusion](https://github.com/w3c/csswg-drafts/issues/6425#issuecomment-907733117) occurred to me when parsing a `<color-stop-list>`, whose syntax requires two color stops but its grammar accepts an implicit color stop defining two stops with the same color.
      author:
         url:https://github.com/cdoublev
         type:Person
         name:cdoublev
      datePublished:2022-11-22T11:04:10.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:3
      url:https://github.com/8122/csswg-drafts/issues/8122
      context:https://schema.org
      headline:[selectors-4] Legacy `:` pseudo-element cannot appear before type/subclass selectors
      articleBody:Chrome/FF seems to parse `:before#id` or `:before.class` as invalid (instead of valid and matching nothing) but I do not see on which part of the spec this is based. > *Pseudo-elements are featureless, and so can’t be matched by any other selector* This does not make them invalid. Legacy `:` pseudo-element syntax is defined in `<subclass-selector>` as a `<pseudo-class-selector>`. > `<compound-selector> = [ <type-selector>? <subclass-selector>* [ <pseudo-element-selector> <pseudo-class-selector>* ]* ]!` Subclass selectors can appear in any order while still selecting the same set of elements, but this is not true for a pseudo-element specified with the legacy single `:` syntax. Therefore I assume that `:before` must be handled as if it has been specified with `::before` and matched `<pseudo-element-selector>`. **If so, it may be helpfull to define it in the spec.** A [similar confusion](https://github.com/w3c/csswg-drafts/issues/6425#issuecomment-907733117) occurred to me when parsing a `<color-stop-list>`, whose syntax requires two color stops but its grammar accepts an implicit color stop defining two stops with the same color.
      author:
         url:https://github.com/cdoublev
         type:Person
         name:cdoublev
      datePublished:2022-11-22T11:04:10.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:3
      url:https://github.com/8122/csswg-drafts/issues/8122
Person:
      url:https://github.com/cdoublev
      name:cdoublev
      url:https://github.com/cdoublev
      name:cdoublev
InteractionCounter:
      interactionType:https://schema.org/CommentAction
      userInteractionCount:3
      interactionType:https://schema.org/CommentAction
      userInteractionCount:3

External Links {🔗}(9)

Analytics and Tracking {📊}

Site Verification - Google

Libraries {📚}

Clipboard.js
D3.js
Lodash

Emails and Hosting {✉️}

Mail Servers:

aspmx.l.google.com
alt1.aspmx.l.google.com
alt2.aspmx.l.google.com
alt3.aspmx.l.google.com
alt4.aspmx.l.google.com

Name Servers:

dns1.p08.nsone.net
dns2.p08.nsone.net
dns3.p08.nsone.net
dns4.p08.nsone.net
ns-1283.awsdns-32.org
ns-1707.awsdns-21.co.uk
ns-421.awsdns-52.com
ns-520.awsdns-01.net

8.7s.