GITHUB . COM {
}
Detected CMS Systems:
- Wordpress (2 occurrences)
Title:
[css-position] Static position of abspos top layer elements inside fixed pos. · Issue #9939 · w3c/csswg-drafts
Description:
This is the cyclic / ordering issue that I was concerned about in #8040. Both Firefox and Blink get it wrong. WebKit gets it right, but I'm not sure what they're doing, maybe they're la...
Website Age:
17 years and 9 months (reg. 2007-10-09).
Matching Content Categories {📚}
- Cryptocurrency
- Automotive
- Music
Content Management System {📝}
What CMS is github.com built with?
Github.com is powered by 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 {🔍}
top, layer, position, emilio, static, abspos, fixed, commented, issue, pos, chrishtr, element, chrome, cssposition, wrong, collaborator, author, content, sign, elements, webkit, rwlbuis, positions, correctly, inside, html, fixedpos, viewport, box, icb, bfgeek, ntm, block, contributor, case, bug, toppx, computing, depend, layout, navigation, open, pull, requests, actions, projects, security, cyclic, theyre, style,
Topics {✒️}
clunky static-pos behavior emilio mentioned [css-position-3] top layer elements anchor position incorrect static position 2px solid blue comment metadata assignees top layer element top layer depending webkit parents top layer depend html element fixed pos top-layer reparenting implementation caching bug static position milestone relationships webkit dialog positions correctly flow position abspos element top-layer' top layer absolute adding top main issue spec issue webcompat issue cyclic problem renders correctly fixed position preferred fix equally trivial continue twisting root scroller extra complications vice versa layout tree completely independent red rectangle race condition feared initially content weird cases layout dependency github block adjustments
Payment Methods {📊}
- Braintree
Questions {❓}
- @bfgeek WDYT?
- @nt1m so webkit parents all top layer elements (abspos and fixed pos) to the viewport rather than the root scroller?
- @rwlbuis do you know what WebKit is doing here?
- Already have an account?
- Also, you can have an abspos in the top layer depend on a fixed pos in the top layer and vice versa too, right?
- I'm confused, so in chrome the top-layer reparenting also reparents the regular in-flow position?
- It doesn't depend on it though, right?
- WebKit gets it right, but I'm not sure what they're doing, maybe they're laying out the abspos twice?
Schema {🗺️}
DiscussionForumPosting:
context:https://schema.org
headline:[css-position] Static position of abspos top layer elements inside fixed pos.
articleBody:This is the cyclic / ordering issue that I was concerned about in #8040.
Both Firefox and Blink get it wrong. WebKit gets it right, but I'm not sure what they're doing, maybe they're laying out the abspos twice?
```html
<!DOCTYPE html>
<meta charset="utf-8">
<style>
#outer {
position: fixed;
width: 200px;
height: 200px;
border: 2px solid blue;
}
dialog {
display: inline;
position: absolute;
inset: auto;
}
</style>
Some content.
<br>
<br>
<br>
<br>
<br>
Some more.
<br>
<div id=outer>
Fixed-pos.
<dialog>Absolute popover inside fixed element</dialog>
</div>
<script>
document.querySelector("dialog").showModal();
</script>
```
The main issue here is that you have:
* Viewport box
* ICB
* Abspos
* Fixedpos
So you lay out the abspos _before_ the fixedpos, and the static position isn't computed yet.
cc @rlbuis @bfgeek @chrishtr
author:
url:https://github.com/emilio
type:Person
name:emilio
datePublished:2024-02-13T01:52:05.000Z
interactionStatistic:
type:InteractionCounter
interactionType:https://schema.org/CommentAction
userInteractionCount:17
url:https://github.com/9939/csswg-drafts/issues/9939
context:https://schema.org
headline:[css-position] Static position of abspos top layer elements inside fixed pos.
articleBody:This is the cyclic / ordering issue that I was concerned about in #8040.
Both Firefox and Blink get it wrong. WebKit gets it right, but I'm not sure what they're doing, maybe they're laying out the abspos twice?
```html
<!DOCTYPE html>
<meta charset="utf-8">
<style>
#outer {
position: fixed;
width: 200px;
height: 200px;
border: 2px solid blue;
}
dialog {
display: inline;
position: absolute;
inset: auto;
}
</style>
Some content.
<br>
<br>
<br>
<br>
<br>
Some more.
<br>
<div id=outer>
Fixed-pos.
<dialog>Absolute popover inside fixed element</dialog>
</div>
<script>
document.querySelector("dialog").showModal();
</script>
```
The main issue here is that you have:
* Viewport box
* ICB
* Abspos
* Fixedpos
So you lay out the abspos _before_ the fixedpos, and the static position isn't computed yet.
cc @rlbuis @bfgeek @chrishtr
author:
url:https://github.com/emilio
type:Person
name:emilio
datePublished:2024-02-13T01:52:05.000Z
interactionStatistic:
type:InteractionCounter
interactionType:https://schema.org/CommentAction
userInteractionCount:17
url:https://github.com/9939/csswg-drafts/issues/9939
Person:
url:https://github.com/emilio
name:emilio
url:https://github.com/emilio
name:emilio
InteractionCounter:
interactionType:https://schema.org/CommentAction
userInteractionCount:17
interactionType:https://schema.org/CommentAction
userInteractionCount:17
External Links {🔗}(5)
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