GITHUB . COM {
}
Detected CMS Systems:
- Wordpress (2 occurrences)
Title:
[selectors-4] Introduce `:popover-open` pseudo class · Issue #8637 · w3c/csswg-drafts
Description:
We recently resolved to add general-purpose :open and :closed pseudo classes, which apply to "things that can open and close". While not defined in CSSWG, the stated intention was to include things like <details>, <select>, <dialog>, and...
Website Age:
17 years and 8 months (reg. 2007-10-09).
Matching Content Categories {📚}
- Dating & Relationships
- Events
- Humor
Content Management System {📝}
What CMS is github.com built with?
Github.com is based on 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 {🔍}
open, popover, closed, element, pseudo, fullscreen, popovers, commented, issue, jhy, mfreed, things, state, contributor, class, details, sign, selectors, popoveropen, apply, jakearchibald, elements, openclosed, separate, react, tabatkins, projects, dialog, multiple, problem, openui, mentioned, dbaron, member, related, semantics, applied, pseudoclasses, distinguish, work, added, keithamus, type, toplayer, navigation, pull, requests, actions, security, introduce,
Topics {✒️}
chromium-wpt-export-bot mentioned mfreed7 mentioned add general-purpose claim general names avoids difficult questions comment metadata assignees separate pseudo-classes closed pseudo class generally work css property overlay closed pseudo classes top-layer pseudo dual-states problem type projects pseudo class multiple element types csswg resolution projects milestone open dialog popover open/closed state dedicated pseudo separate attribute element type top-layer top layer recently resolved csswg open state popover-open popover replaces popover communicate open dialog stated intention vice versa bit unclear unexpected intersections reasonable suggestion pretty reasonable multiple definitions kinda falls naming reasons removing support refers specifically javascript method milestone relationships details[popover] open/closed expanded details specific elements element semantics
Payment Methods {📊}
- Braintree
Questions {❓}
- @dbaron @tabatkins should :open apply to popovers as well as :popover, or is :popover instead of :open?
- @jh3y do you know of any popover use cases that would be harmed by not having access to a :closed pseudo class?
- Already have an account?
- Could all elements that are in the top-layer have a :top-layer pseudo?
- Is it ok for popover to claim general names like :open and :closed?
- The only issue I see is "Does :popover communicate that state well?
Schema {🗺️}
DiscussionForumPosting:
context:https://schema.org
headline:[selectors-4] Introduce `:popover-open` pseudo class
articleBody:We [recently resolved](https://github.com/w3c/csswg-drafts/issues/7319#issuecomment-1276473056) to add general-purpose `:open` and `:closed` pseudo classes, which apply to "things that can open and close". While not defined in CSSWG, the stated [intention](https://github.com/w3c/csswg-drafts/issues/7319#issuecomment-1242377579) was to include things like `<details>`, `<select>`, `<dialog>`, and Popover.
@jakearchibald recently [raised](https://github.com/whatwg/html/issues/9055) the issue that in some cases, this is ambiguous, because there are multiple "ways" that something can be open or closed, and both might apply at the same time. Take, as an example, `<details popover>`, which can be "open" as a popover, but "closed" as a details, or vice versa. There's no way for these to be disambiguated on the basis of `:open` or `:closed` alone.
It is a bit unclear whether fullscreen elements should be included as "something that can open and close", but it's possible. That allows the possibility of a fullscreen `<details>` element which can be both open and closed. But fullscreen elements have a dedicated pseudo, `:fullscreen`, which allows one to disambiguate that state of openness vs. others.
It would seem that we need another such pseudo for popovers, because any element can also be a popover, and can therefore run into this dual-states problem. We discussed this in OpenUI, and [proposed `:popover`](https://github.com/whatwg/html/issues/9055#issuecomment-1481493678) as a pseudo class that applies only to popovers that are open (as a popover). That would allow developers to do:
```css
details[popover]:closed:popover {
/* styles for a non-expanded details that is open as a popover */
}
```
author:
url:https://github.com/mfreed7
type:Person
name:mfreed7
datePublished:2023-03-23T17:14:31.000Z
interactionStatistic:
type:InteractionCounter
interactionType:https://schema.org/CommentAction
userInteractionCount:20
url:https://github.com/8637/csswg-drafts/issues/8637
context:https://schema.org
headline:[selectors-4] Introduce `:popover-open` pseudo class
articleBody:We [recently resolved](https://github.com/w3c/csswg-drafts/issues/7319#issuecomment-1276473056) to add general-purpose `:open` and `:closed` pseudo classes, which apply to "things that can open and close". While not defined in CSSWG, the stated [intention](https://github.com/w3c/csswg-drafts/issues/7319#issuecomment-1242377579) was to include things like `<details>`, `<select>`, `<dialog>`, and Popover.
@jakearchibald recently [raised](https://github.com/whatwg/html/issues/9055) the issue that in some cases, this is ambiguous, because there are multiple "ways" that something can be open or closed, and both might apply at the same time. Take, as an example, `<details popover>`, which can be "open" as a popover, but "closed" as a details, or vice versa. There's no way for these to be disambiguated on the basis of `:open` or `:closed` alone.
It is a bit unclear whether fullscreen elements should be included as "something that can open and close", but it's possible. That allows the possibility of a fullscreen `<details>` element which can be both open and closed. But fullscreen elements have a dedicated pseudo, `:fullscreen`, which allows one to disambiguate that state of openness vs. others.
It would seem that we need another such pseudo for popovers, because any element can also be a popover, and can therefore run into this dual-states problem. We discussed this in OpenUI, and [proposed `:popover`](https://github.com/whatwg/html/issues/9055#issuecomment-1481493678) as a pseudo class that applies only to popovers that are open (as a popover). That would allow developers to do:
```css
details[popover]:closed:popover {
/* styles for a non-expanded details that is open as a popover */
}
```
author:
url:https://github.com/mfreed7
type:Person
name:mfreed7
datePublished:2023-03-23T17:14:31.000Z
interactionStatistic:
type:InteractionCounter
interactionType:https://schema.org/CommentAction
userInteractionCount:20
url:https://github.com/8637/csswg-drafts/issues/8637
Person:
url:https://github.com/mfreed7
name:mfreed7
url:https://github.com/mfreed7
name:mfreed7
InteractionCounter:
interactionType:https://schema.org/CommentAction
userInteractionCount:20
interactionType:https://schema.org/CommentAction
userInteractionCount:20
External Links {🔗}(4)
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