
GITHUB . COM {
}
Detected CMS Systems:
- Wordpress (2 occurrences)
Title:
[popup] More crisply define the interactions between `popup=popup`, `popup=hint`, and `popup=async` Β· Issue #525 Β· openui/open-ui
Description:
The explainer has a section dedicated to the behaviors of each of these popup types, but there are some gaps: Should "nested" popup=hint (tooltips) be allowed, in the same way that popup=popup is allowed to nest? It seems like tooltips a...
Website Age:
17 years and 9 months (reg. 2007-10-09).
Matching Content Categories {π}
- Dating & Relationships
- Events
- Social Networks
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 {π}
popup, tooltip, tooltips, open, mfreed, popuppopup, default, element, popuphint, shown, page, commented, agenda, popupasync, allowed, added, ill, load, scottaohara, collaborator, focus, attribute, call, define, issue, opened, nested, initiallyopen, defaultopen, div, agreed, meeting, show, ancestral, sign, crisply, interactions, nest, hidden, popover, behavior, hint, moving, author, label, youd, topic, cssmeetingbot, word, triggering,
Topics {βοΈ}
popover api type assigned labels popover directly enter/interact full irc log popup=hint ui meeting today mfreed7 closed initially opened popups nested tooltips prohibited comment metadata assignees personal information [popup] supported activatable element popup=popup displayed popup=hint works popup=hint displayed menu popup user specifically invoked proposed rules https type projects projects milestone initial tooltip popup close thepopup=hint content attributes discussion generally including ancestral tooltips default popup behavior ui folks descendent triggering element open popup open tooltips opened popup tooltips nested nested tooltips open popups stay open nested inside popup=async content popup=popup `popup=popup` receiving focus / receive focus / hover/focus moved focus tooltip opened popup=hint hint popup `popup=hint` proposed behavior descriptive information
Payment Methods {π}
- Braintree
Questions {β}
- Already have an account?
- But are there thoughts about the above?
- But are there use cases for tooltips nested within tooltips?
- But maybe I missed a way for this to happen?
- Seriously wondering if a hint should even be allowed to be open by default?
- Should "nested" popup=hint (tooltips) be allowed, in the same way that popup=popup is allowed to nest?
- Should popup=popup be allowed to "nest" inside tooltips?
- Since a hint/tooltip would otherwise only be revealed on hover/focus of the element it describes, and auto-dismiss when someone hovered or moved focus away from the invoking element, wouldn't having it open by default result in an immediate closure once someone starting moving keyboard focus or moving their mouse?
- Someone navigating the page sequentially with keyboard would come to that other element first, its tooltip popup would be invoked, and then would that not close the initially opened tooltip popup?
- When a tooltip is shown while there are open popups, and then the topmost popup is hidden (either with light dismiss or via hidePopup()), should the tooltip be hidden also?
- [Popup] Should light dismiss be cancellable on popup?
- From what i gather here i also think yes?
Schema {πΊοΈ}
DiscussionForumPosting:
context:https://schema.org
headline:[popup] More crisply define the interactions between `popup=popup`, `popup=hint`, and `popup=async`
articleBody:The explainer has [a section dedicated to the behaviors](https://github.com/openui/open-ui/blob/main/research/src/pages/popup/popup.research.explainer.mdx#classes-of-ui---dismiss-behavior-and-interactions) of each of these popup types, but there are some gaps:
1. Should "nested" `popup=hint` (tooltips) be allowed, in the same way that `popup=popup` is allowed to nest? It seems like tooltips and other `popup=hint` UI should really be constrained to be **exactly** "one at a time", with nested tooltips prohibited. But are there use cases for tooltips nested within tooltips?
2. Should `popup=popup` be allowed to "nest" inside tooltips? Again here, it seems like the answer should be no, but perhaps there are use cases?
3. When a tooltip is shown while there are open popups, and then the topmost popup is hidden (either with light dismiss or via `hidePopup()`), should the tooltip be hidden also? It seems like "yes", but what do UI folks think?
4. How should `initiallyopen` (maybe [renamed](https://github.com/openui/open-ui/issues/500) to `defaultopen` soon) behave when there are all three popup types. It would seem that only the first occurence of either `<div popup=popup initiallyopen>` **or** `<div popup=hint initiallyopen>` should be shown upon page load. It would also seem that an unlimited number of `<div popup=async initiallyopen>` should be auto-shown on load, independent of `popup=popup` or `popup=hint`.
I have [a CL](https://chromium-review.googlesource.com/c/chromium/src/+/3606540) up to implement my best guesses at the above questions, so perhaps an easy way to get answers is for folks to wait for that to land in a Chromium Canary and test it out. But thoughts appreciated.
author:
url:https://github.com/mfreed7
type:Person
name:mfreed7
datePublished:2022-04-27T23:31:13.000Z
interactionStatistic:
type:InteractionCounter
interactionType:https://schema.org/CommentAction
userInteractionCount:10
url:https://github.com/525/open-ui/issues/525
context:https://schema.org
headline:[popup] More crisply define the interactions between `popup=popup`, `popup=hint`, and `popup=async`
articleBody:The explainer has [a section dedicated to the behaviors](https://github.com/openui/open-ui/blob/main/research/src/pages/popup/popup.research.explainer.mdx#classes-of-ui---dismiss-behavior-and-interactions) of each of these popup types, but there are some gaps:
1. Should "nested" `popup=hint` (tooltips) be allowed, in the same way that `popup=popup` is allowed to nest? It seems like tooltips and other `popup=hint` UI should really be constrained to be **exactly** "one at a time", with nested tooltips prohibited. But are there use cases for tooltips nested within tooltips?
2. Should `popup=popup` be allowed to "nest" inside tooltips? Again here, it seems like the answer should be no, but perhaps there are use cases?
3. When a tooltip is shown while there are open popups, and then the topmost popup is hidden (either with light dismiss or via `hidePopup()`), should the tooltip be hidden also? It seems like "yes", but what do UI folks think?
4. How should `initiallyopen` (maybe [renamed](https://github.com/openui/open-ui/issues/500) to `defaultopen` soon) behave when there are all three popup types. It would seem that only the first occurence of either `<div popup=popup initiallyopen>` **or** `<div popup=hint initiallyopen>` should be shown upon page load. It would also seem that an unlimited number of `<div popup=async initiallyopen>` should be auto-shown on load, independent of `popup=popup` or `popup=hint`.
I have [a CL](https://chromium-review.googlesource.com/c/chromium/src/+/3606540) up to implement my best guesses at the above questions, so perhaps an easy way to get answers is for folks to wait for that to land in a Chromium Canary and test it out. But thoughts appreciated.
author:
url:https://github.com/mfreed7
type:Person
name:mfreed7
datePublished:2022-04-27T23:31:13.000Z
interactionStatistic:
type:InteractionCounter
interactionType:https://schema.org/CommentAction
userInteractionCount:10
url:https://github.com/525/open-ui/issues/525
Person:
url:https://github.com/mfreed7
name:mfreed7
url:https://github.com/mfreed7
name:mfreed7
InteractionCounter:
interactionType:https://schema.org/CommentAction
userInteractionCount:10
interactionType:https://schema.org/CommentAction
userInteractionCount:10
External Links {π}(3)
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