GITHUB . COM {}

Matching Content Categories {📚}

• Graphic Design
• Video & Online Content
• News & Politics

Content Management System {📝}

What CMS is github.com built with?

Github.com utilizes 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 {💳}

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

size, suggestion, flex, div, item, height, davidsgrogan, blue, width, automatic, box, minimum, firefox, behavior, commented, orange, items, main, change, minintrinsic, final, content, contentsize, mincontent, issue, aspectratio, member, fantasai, percentage, cssflexbox, chrome, preferred, tabatkins, sign, closed, spec, computed, sizes, added, transferred, current, author, gecko, aethanyc, boxs, projects, element, block, styledisplay, httpsjsfiddlenetdgrogansdfr,

Topics {✒️}

change content-size suggestion content-based minimum size /css-flexbox-1/overview tabatkins edits member davidsgrogan added css working group min-content contribution current spec implies content size suggestion [css-sizing-4] automatic minimum sizing interop problem discussed cyclic percentage rules size suggestion exists transferred size suggestion min-content size type projects automatic minimum size main size property aspect-ratio affect preferred main size preferred=] [=main size=] constraints makes sense full irc log similarly meaningful shrinkability net/dgrogan/2734sdfr/ 5px solid orange flex base size automatic minimum width apply aspect-ratio' automatic minimum height automatic definite sizes identical block box comment metadata assignees projects milestone bs index 2c3418beb give flexbox op flex container min-content unflexed flex items applies flexbox' size suggestion agrees final width minimum size change behavior blink matches gecko underlying behavior difference aspect-ratio aspect-ratio' aspect ratio

Payment Methods {📊}

• Braintree

Questions {❓}

• @tabatkins @fantasai , what do we do in the case of a flex item with an aspect ratio?
• Already have an account?
• Should they be different?
• The CSS Working Group just discussed [css-flexbox] Change content-size suggestion to min-intrinsic instead of min-content?
• [css-flexbox] Change content-size suggestion to min-intrinsic instead of min-content?
• Change content-size suggestion to be min-intrinsic[1] instead of min-content (@bfgeek previously floated this idea In [css-sizing-4] Should aspect-ratio affect the intrinsic size?
• Net/dgrogan/2734sdfr/ has automatic minimum width of 100px?
• Or maybe Gecko floors the entire automatic minimum size?

Schema {🗺️}

DiscussionForumPosting:
      context:https://schema.org
      headline:[css-flexbox] Change content-size suggestion to min-intrinsic instead of min-content?
      articleBody:https://drafts.csswg.org/css-flexbox/#min-size-auto This issue stems from an interop problem discussed in https://github.com/web-platform-tests/wpt/commit/21a7c47ad593720b0fed693390884bf8570a8d0c . In the example below, the spec dictates a final width of the flex item of `50px`. But when the same element is a block box it has width `100px`. Should they be different? ```html <div style="display: flex;"> <!-- Chrome and spec say final width is 50px. Firefox says 100px. --> <div style="background: blue; height: 100px; aspect-ratio: 1/2; "> <div style="width: 100px;"></div> </div> </div> <!-- Everyone agrees final width is 100px --> <div style="background: blue; height: 100px; aspect-ratio: 1/2; "> <div style="width: 100px;"></div> </div> ``` https://jsfiddle.net/dgrogan/2734sdfr/ Of course a flex item can have a different final size than an otherwise-identical block box because the whole point of a flex container is that it flexes the items. But this item is **not** flexed, and it's still a different size. That seems weird. In more detail, the difference in this case is a result of aspect-ratio's automatic minimum size being more aggressive than flexbox's. Giving flex a weaker set of constraints makes sense, because we want to give flexbox the power to flex its items. But it is puzzlement-inducing that putting a no-op flex container around an element changes the element's size. Possible solution if we want the boxes to be the same width whether they are block boxes or unflexed flex items (i.e. Firefox's behavior today): 1. change content-size suggestion to be min-intrinsic[1] instead of min-content (@bfgeek previously floated this idea In https://github.com/w3c/csswg-drafts/issues/5032#issuecomment-644517090) 2. Then we'd also have to change specified size suggestion to only account for computed main size properties, not preferred sizes that come from the aspect-ratio. As is, specified size suggestion is 50px, so even we did (1) and only (1), the final width of the item would still be 50px. Or, do whatever Firefox is doing, which is probably not those. But, if giving the blue box different sizes in the two layout modes doesn't strike anyone else as weird, then maybe we just close this issue and discard the idea of making content-size suggestion = min-intrinsic. Even if we do that, we still need to determine which of Firefox and Chrome behavior is correct. [1] or whatever the name is, vis-a-vis https://github.com/w3c/csswg-drafts/issues/5305
      author:
         url:https://github.com/davidsgrogan
         type:Person
         name:davidsgrogan
      datePublished:2021-11-04T02:31:37.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:66
      url:https://github.com/6794/csswg-drafts/issues/6794
      context:https://schema.org
      headline:[css-flexbox] Change content-size suggestion to min-intrinsic instead of min-content?
      articleBody:https://drafts.csswg.org/css-flexbox/#min-size-auto This issue stems from an interop problem discussed in https://github.com/web-platform-tests/wpt/commit/21a7c47ad593720b0fed693390884bf8570a8d0c . In the example below, the spec dictates a final width of the flex item of `50px`. But when the same element is a block box it has width `100px`. Should they be different? ```html <div style="display: flex;"> <!-- Chrome and spec say final width is 50px. Firefox says 100px. --> <div style="background: blue; height: 100px; aspect-ratio: 1/2; "> <div style="width: 100px;"></div> </div> </div> <!-- Everyone agrees final width is 100px --> <div style="background: blue; height: 100px; aspect-ratio: 1/2; "> <div style="width: 100px;"></div> </div> ``` https://jsfiddle.net/dgrogan/2734sdfr/ Of course a flex item can have a different final size than an otherwise-identical block box because the whole point of a flex container is that it flexes the items. But this item is **not** flexed, and it's still a different size. That seems weird. In more detail, the difference in this case is a result of aspect-ratio's automatic minimum size being more aggressive than flexbox's. Giving flex a weaker set of constraints makes sense, because we want to give flexbox the power to flex its items. But it is puzzlement-inducing that putting a no-op flex container around an element changes the element's size. Possible solution if we want the boxes to be the same width whether they are block boxes or unflexed flex items (i.e. Firefox's behavior today): 1. change content-size suggestion to be min-intrinsic[1] instead of min-content (@bfgeek previously floated this idea In https://github.com/w3c/csswg-drafts/issues/5032#issuecomment-644517090) 2. Then we'd also have to change specified size suggestion to only account for computed main size properties, not preferred sizes that come from the aspect-ratio. As is, specified size suggestion is 50px, so even we did (1) and only (1), the final width of the item would still be 50px. Or, do whatever Firefox is doing, which is probably not those. But, if giving the blue box different sizes in the two layout modes doesn't strike anyone else as weird, then maybe we just close this issue and discard the idea of making content-size suggestion = min-intrinsic. Even if we do that, we still need to determine which of Firefox and Chrome behavior is correct. [1] or whatever the name is, vis-a-vis https://github.com/w3c/csswg-drafts/issues/5305
      author:
         url:https://github.com/davidsgrogan
         type:Person
         name:davidsgrogan
      datePublished:2021-11-04T02:31:37.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:66
      url:https://github.com/6794/csswg-drafts/issues/6794
Person:
      url:https://github.com/davidsgrogan
      name:davidsgrogan
      url:https://github.com/davidsgrogan
      name:davidsgrogan
InteractionCounter:
      interactionType:https://schema.org/CommentAction
      userInteractionCount:66
      interactionType:https://schema.org/CommentAction
      userInteractionCount:66

External Links {🔗}(7)

• What are the total earnings of https://github.blog?
• What's the financial outcome of https://drafts.csswg.org/css-flexbox/#min-size-auto?
• Get to know what's the income of https://jsfiddle.net/dgrogan/2734sdfr/
• How much profit does https://drafts.csswg.org/css-sizing-4/#aspect-ratio-minimum make?
• How much revenue does https://drafts.csswg.org/css-flexbox-1/#min-size-auto bring in?
• How much does https://www.w3.org/TR/css-sizing-3/#cyclic-percentage-contribution net monthly?
• https://www.githubstatus.com/'s total income per month

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