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/w3c/csswg-drafts/issues/6476.

Title:
[css-flexbox-1] When can available space for flex items be infinite? · Issue #6476 · w3c/csswg-drafts
Description:
I’m implementing Step 2: determine the available main and cross space for the flex items, and I’m trying to better understand what constitutes definite and indefinite sizes, and by extension definite and infinite available space. CSS Box...
Website Age:
17 years and 8 months (reg. 2007-10-09).

Matching Content Categories {📚}

Graphic Design
DIY & Home Improvement
Dating & Relationships

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

flex, space, infinite, definite, size, layout, container, andyjakubowski, sizes, cssflexbox, issue, closed, tabatkins, question, sign, items, block, inline, answered, fantasai, projects, resolved, blocksize, percentage, orthogonal, commented, commenter, response, content, navigation, pull, requests, actions, security, indefinite, css, box, sizing, performing, initial, blocks, element, wasnt, intrinsic, rely, cases, identify, computes, auto, flow,

Topics {✒️}

personal information [css-flexbox-1] [css-flexbox] clarify commenter response max-content size tabatkins closed �stretch-fit” sizing orthogonal flow roots block-size depends flex container size activity andyjakubowski mentioned flex container participates assigned labels closed type projects fallback size defined intrinsic sizes counted treat intrinsic sizes replaced blocks [css2] wm clamping rule answer helped clarify comment metadata assignees absolutely positioned element identify definite sizes indefinite sizes initial layout pass fantasai reopened resolved solely flex container projects milestone auto-sizing flexbox definite sizes block axis inline size flex items content constitutes definite extension definite resolved performing layout �performing layout” �real layout” orthogonal flows completed sign implementing step 2 line-wrapping shrink-wrapping wg resolution default approaching cyclic dependency inline dimension

Payment Methods {📊}

Braintree

Questions {❓}

Already have an account?
[css-flexbox-1] When can available space for flex items be infinite?
Alternatively, how should one interpret phrases like “performing layout”, or “real layout” when trying to identify definite sizes which shouldn’t rely on layout?
Is there a finite list of cases where available space for flex items can be infinite?

Schema {🗺️}

DiscussionForumPosting:
      context:https://schema.org
      headline:[css-flexbox-1] When can available space for flex items be infinite?
      articleBody:I’m implementing [Step 2: determine the available main and cross space for the flex items](https://drafts.csswg.org/css-flexbox-1/#algo-available), and I’m trying to better understand what constitutes definite and indefinite sizes, and by extension definite and infinite available space. [CSS Box Sizing Level 3](https://drafts.csswg.org/css-sizing-3) defines [definite size](https://drafts.csswg.org/css-sizing-3/#definite) as: > A size that can be determined without performing layout; that is, a <length>, a measure of text (without consideration of line-wrapping), a size of the initial containing block, or a <percentage> or other formula (such the “stretch-fit” sizing of non-replaced blocks [CSS2]) that is resolved solely against definite sizes. > Additionally, the size of the containing block of an absolutely positioned element is always definite with respect to that element. It wasn’t clear to me if intrinsic sizes counted as definite, and after some digging found [[css-sizing] definite sizes and shrink-wrapping](https://lists.w3.org/Archives/Public/www-style/2016May/0244.html) and the [WG resolution](https://www.w3.org/2016/05/09-css-irc#T21-51-29) saying that: > treat intrinsic sizes as definite when they don't rely on layout, by default Approaching this from another angle, I tried to think if situations where the available space could possibly be infinite. These are the cases I was able to identify: - flex container `block-size` computes to `auto`, and the flex container participates in flow layout - flex container `block-size` computes to a `<percentage>`, and the containing block’s `block-size` depends on content; this creates a cyclic dependency, so `<percentage>` behaves as `auto` Interestingly, I wasn’t able to think of one situation where the available space in the inline dimension of the flex container would ever be infinite. Even in orthogonal flows the inline size of the flex container seems to be resolved against a fallback size defined in [Available Space in Orthogonal Flows](https://drafts.csswg.org/css-writing-modes-4/#orthogonal-auto). I was unable to reproduce the case where the flex container would lay its box out at its `max-content` size when given “infinite available inline space” as described in [Auto-sizing Other Orthogonal Flow Roots](https://drafts.csswg.org/css-writing-modes-4/#orthogonal-layout). So I have two questions: - is there a finite list of cases where available space for flex items can be infinite? Is my list correct? - alternatively, how should one interpret phrases like “performing layout”, or “real layout” when trying to identify definite sizes which shouldn’t rely on layout?
      author:
         url:https://github.com/andyjakubowski
         type:Person
         name:andyjakubowski
      datePublished:2021-07-27T10:18:24.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:3
      url:https://github.com/6476/csswg-drafts/issues/6476
      context:https://schema.org
      headline:[css-flexbox-1] When can available space for flex items be infinite?
      articleBody:I’m implementing [Step 2: determine the available main and cross space for the flex items](https://drafts.csswg.org/css-flexbox-1/#algo-available), and I’m trying to better understand what constitutes definite and indefinite sizes, and by extension definite and infinite available space. [CSS Box Sizing Level 3](https://drafts.csswg.org/css-sizing-3) defines [definite size](https://drafts.csswg.org/css-sizing-3/#definite) as: > A size that can be determined without performing layout; that is, a <length>, a measure of text (without consideration of line-wrapping), a size of the initial containing block, or a <percentage> or other formula (such the “stretch-fit” sizing of non-replaced blocks [CSS2]) that is resolved solely against definite sizes. > Additionally, the size of the containing block of an absolutely positioned element is always definite with respect to that element. It wasn’t clear to me if intrinsic sizes counted as definite, and after some digging found [[css-sizing] definite sizes and shrink-wrapping](https://lists.w3.org/Archives/Public/www-style/2016May/0244.html) and the [WG resolution](https://www.w3.org/2016/05/09-css-irc#T21-51-29) saying that: > treat intrinsic sizes as definite when they don't rely on layout, by default Approaching this from another angle, I tried to think if situations where the available space could possibly be infinite. These are the cases I was able to identify: - flex container `block-size` computes to `auto`, and the flex container participates in flow layout - flex container `block-size` computes to a `<percentage>`, and the containing block’s `block-size` depends on content; this creates a cyclic dependency, so `<percentage>` behaves as `auto` Interestingly, I wasn’t able to think of one situation where the available space in the inline dimension of the flex container would ever be infinite. Even in orthogonal flows the inline size of the flex container seems to be resolved against a fallback size defined in [Available Space in Orthogonal Flows](https://drafts.csswg.org/css-writing-modes-4/#orthogonal-auto). I was unable to reproduce the case where the flex container would lay its box out at its `max-content` size when given “infinite available inline space” as described in [Auto-sizing Other Orthogonal Flow Roots](https://drafts.csswg.org/css-writing-modes-4/#orthogonal-layout). So I have two questions: - is there a finite list of cases where available space for flex items can be infinite? Is my list correct? - alternatively, how should one interpret phrases like “performing layout”, or “real layout” when trying to identify definite sizes which shouldn’t rely on layout?
      author:
         url:https://github.com/andyjakubowski
         type:Person
         name:andyjakubowski
      datePublished:2021-07-27T10:18:24.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:3
      url:https://github.com/6476/csswg-drafts/issues/6476
Person:
      url:https://github.com/andyjakubowski
      name:andyjakubowski
      url:https://github.com/andyjakubowski
      name:andyjakubowski
InteractionCounter:
      interactionType:https://schema.org/CommentAction
      userInteractionCount:3
      interactionType:https://schema.org/CommentAction
      userInteractionCount:3

External Links {🔗}(9)

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

9.57s.