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/w3ctag/design-reviews/issues/680.

Title:
HTMLPopupElement · Issue #680 · w3ctag/design-reviews
Description:
Braw mornin' TAG! (That's a new one for me 😄 ) I'm requesting a TAG review of the <popup> element. This is effectively a re-opening of the previously requested TAG review for this...
Website Age:
17 years and 9 months (reg. 2007-10-09).

Matching Content Categories {📚}

Video & Online Content
Social Networks
Education

Content Management System {📝}

What CMS is github.com built with?

Github.com is built with 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 5,013,426 paying customers.
The estimated monthly recurring revenue (MRR) is $21,056,387.
The estimated annual recurring revenues (ARR) are $252,676,649.

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 {🔍}

element, dialog, popup, issue, review, specification, aria, toasts, mfreed, tag, tooltips, dialogs, behaviors, open, domenic, role, explainer, menus, similar, semantic, teaching, issues, elements, roles, accessibility, content, menu, feature, comment, html, spec, platform, major, commented, ive, number, qualities, controls, suggestions, tooltip, sign, draft, prefer, progress, raised, httpsgithubcomopenuiopenuilabelspopup, openuiopenui, give, proposal, roledialog,

Topics {✒️}

fyi/results/html/semantics/interactive-elements/ /openui/open-ui/labels/popup /openui/open-ui/issues major unresolved issues existing multi-stakeholder review general-purpose top-layer elements domenic edits member org/components/popup tests research security popup-element user research type projects tag provide feedback 31 open issues whatwg html spec %3aopen+label%3apopup org/components/popup info provided topic microsoft key pieces prefer feedback filed actions a-time rule totally valid point form element suggestions major issue current feature champion wrote spec draft map accessibility roles similar semantic space open issue anchor positioning feature //open-ui tag review mfreed7 mentioned content pickers explainer specification url privacy top layer ui elements big issue defaulting issue declaratively open previously microsoft ui purposes teaching ui leaverou atanassov specific purpose html type semantic space removed progress

Payment Methods {📊}

Braintree

Questions {❓}

Already have an account?
Both s and s are general-purpose top-layer elements, and are perhaps close enough to each other to share a role?
In general, the element is already in a somewhat similar boat, no?
It is also sub-par from an accessibility POV for many reasons, including the aforementioned re-parenting, plus the fact that
/ soup doesn't get announced at all by AT, right?
So are you saying you'd prefer to see a proposal for many new elements, all with the same basic behavior (the three qualities I mentioned in my last comment), but different accessibility roles and semantic meaning?
So are you saying you'd prefer to see a proposal for many new elements, all with the same basic behavior (the three qualities I mentioned in my last comment), but different accessibility roles and semantic meaning?
That is, is this for tooltips, menus, toasts?
What is the ARIA role for each of these?
What is the semantic role for ?
Com/openui/open-ui/issues?

Schema {🗺️}

DiscussionForumPosting:
      context:https://schema.org
      headline:HTMLPopupElement
      articleBody:Braw mornin' TAG! (That's a new one for me 😄 ) I'm requesting a TAG review of the `<popup>` element. This is effectively a re-opening of the [previously requested TAG review for this feature](https://github.com/w3ctag/design-reviews/issues/599). That review was closed, waiting for the proposed "Anchor Positioning" feature to be available for review. Please see [this comment](https://github.com/w3ctag/design-reviews/issues/599#issuecomment-863632279) on the old review, linking to the explainer for Anchor Positioning, plus some additional context. Essentially, the Anchor Positioning feature now has an explainer and a significant amount of brainstorming is happening around the [shape of the API](https://docs.google.com/presentation/d/1g0kCtpbGHqzJybhrP1vgbQapXSZW3zMopYOjNfBf0OQ/edit#slide=id.p). From those links you should be able to get a sense for what will be possible, positioning-wise, for `<popup>`. And hopefully that's enough to re-open and continue the TAG review for `<popup>`. In the time since the last TAG review, a [draft specification has been written](https://open-ui.org/components/popup) and reviewed by editors of the WHATWG HTML spec. And a prototype implementation in Chromium is basically complete. Several of the comments on the prior TAG review lead to changes that have been made in the spec and implementation, e.g. the addition of an `initiallyopen` attribute to declaratively open the popup. - Explainer¹: https://open-ui.org/components/popup.research.explainer - Specification URL: https://open-ui.org/components/popup - Tests: https://wpt.fyi/results/html/semantics/interactive-elements/the-popup-element - User research: https://open-ui.org/components/popup.research - Security and Privacy self-review²: - GitHub repo (if you prefer feedback filed there): - Primary contacts (and their relationship to the specification): - Mason Freed (@mfreed7), Google (current feature champion) - Melanie Richards (@melanierichards), Netlify, previously Microsoft (previous champion, wrote spec draft) - Organization(s)/project(s) driving the specification: OpenUI, Google, Microsoft - Key pieces of existing multi-stakeholder review or discussion of this specification: [Prior TAG review](https://github.com/w3ctag/design-reviews/issues/599) - External status/issue trackers for this specification: https://github.com/openui/open-ui/issues?q=is%3Aissue+is%3Aopen+label%3Apopup Further details: - [X] I have reviewed the TAG's [Web Platform Design Principles](https://w3ctag.github.io/design-principles/) - Relevant time constraints or deadlines: None - The group where the work on this specification is currently being done: [OpenUI](https://open-ui.org/) - The group where standardization of this work is intended to be done: WHATWG HTML/DOM - Major unresolved issues with or opposition to this specification: None that I know of - This work is being funded by: Google & Microsoft You should also know that... I appreciate the TAG. 👍 We'd prefer the TAG provide feedback as (please delete all but the desired option): 💬 leave review feedback as a **comment in this issue** and @-notify @mfreed7
      author:
         url:https://github.com/mfreed7
         type:Person
         name:mfreed7
      datePublished:2021-09-28T20:17:57.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:13
      url:https://github.com/680/design-reviews/issues/680
      context:https://schema.org
      headline:HTMLPopupElement
      articleBody:Braw mornin' TAG! (That's a new one for me 😄 ) I'm requesting a TAG review of the `<popup>` element. This is effectively a re-opening of the [previously requested TAG review for this feature](https://github.com/w3ctag/design-reviews/issues/599). That review was closed, waiting for the proposed "Anchor Positioning" feature to be available for review. Please see [this comment](https://github.com/w3ctag/design-reviews/issues/599#issuecomment-863632279) on the old review, linking to the explainer for Anchor Positioning, plus some additional context. Essentially, the Anchor Positioning feature now has an explainer and a significant amount of brainstorming is happening around the [shape of the API](https://docs.google.com/presentation/d/1g0kCtpbGHqzJybhrP1vgbQapXSZW3zMopYOjNfBf0OQ/edit#slide=id.p). From those links you should be able to get a sense for what will be possible, positioning-wise, for `<popup>`. And hopefully that's enough to re-open and continue the TAG review for `<popup>`. In the time since the last TAG review, a [draft specification has been written](https://open-ui.org/components/popup) and reviewed by editors of the WHATWG HTML spec. And a prototype implementation in Chromium is basically complete. Several of the comments on the prior TAG review lead to changes that have been made in the spec and implementation, e.g. the addition of an `initiallyopen` attribute to declaratively open the popup. - Explainer¹: https://open-ui.org/components/popup.research.explainer - Specification URL: https://open-ui.org/components/popup - Tests: https://wpt.fyi/results/html/semantics/interactive-elements/the-popup-element - User research: https://open-ui.org/components/popup.research - Security and Privacy self-review²: - GitHub repo (if you prefer feedback filed there): - Primary contacts (and their relationship to the specification): - Mason Freed (@mfreed7), Google (current feature champion) - Melanie Richards (@melanierichards), Netlify, previously Microsoft (previous champion, wrote spec draft) - Organization(s)/project(s) driving the specification: OpenUI, Google, Microsoft - Key pieces of existing multi-stakeholder review or discussion of this specification: [Prior TAG review](https://github.com/w3ctag/design-reviews/issues/599) - External status/issue trackers for this specification: https://github.com/openui/open-ui/issues?q=is%3Aissue+is%3Aopen+label%3Apopup Further details: - [X] I have reviewed the TAG's [Web Platform Design Principles](https://w3ctag.github.io/design-principles/) - Relevant time constraints or deadlines: None - The group where the work on this specification is currently being done: [OpenUI](https://open-ui.org/) - The group where standardization of this work is intended to be done: WHATWG HTML/DOM - Major unresolved issues with or opposition to this specification: None that I know of - This work is being funded by: Google & Microsoft You should also know that... I appreciate the TAG. 👍 We'd prefer the TAG provide feedback as (please delete all but the desired option): 💬 leave review feedback as a **comment in this issue** and @-notify @mfreed7
      author:
         url:https://github.com/mfreed7
         type:Person
         name:mfreed7
      datePublished:2021-09-28T20:17:57.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:13
      url:https://github.com/680/design-reviews/issues/680
Person:
      url:https://github.com/mfreed7
      name:mfreed7
      url:https://github.com/mfreed7
      name:mfreed7
InteractionCounter:
      interactionType:https://schema.org/CommentAction
      userInteractionCount:13
      interactionType:https://schema.org/CommentAction
      userInteractionCount:13

External Links {🔗}(11)

Analytics and Tracking {📊}

Site Verification - Google

Libraries {📚}

Clipboard.js
D3.js
GSAP
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

9.08s.