Re: [csswg-drafts] [css-grid] Define item processing order when resolving intrinsic track sizes (#10095)

> in which order to process items that cross a flexible track

All such tracks are handled simultaneously in https://drafts.csswg.org/css-grid-2/#algo-spanning-flex-items

> in which order to to process items that do not cross a flexible track and cross the same number of tracks as each other

These are also handled simultaneously (grouped by span size) in https://drafts.csswg.org/css-grid-2/#algo-spanning-items

Note that https://drafts.csswg.org/css-grid-2/#distribute-extra-space works on a set of intrinsic sizes (from the various items that are simultaneously handled). And the order doesn't matter, as noted:

> Maintain separately for each affected track a planned increase, initially set to 0. (This prevents the size increases from becoming order-dependent.)

Initially:
 - 1st column: base size = 0px, growth limit = infinity
 - 2nd column: base size = 0px, growth limit = infinity
 - 3rd column: base size = 0px, growth limit = infinity

We 1st handle the 1st item (spans a single non-flexible column):
 - 1st column: base size = 100px, growth limit = 100px
 - 2nd column: base size = 0px, growth limit = infinity
 - 3rd column: base size = 0px, growth limit = infinity

Then the 3rd item (spans 2 non-flexible columns):
 - 1st column: base size = 100px, growth limit = 100px
 - 2nd column: base size = 20px, growth limit = 20px
 - 3rd column: base size = 0px, growth limit = infinity

Then the 2nd item (crosses a flexible column):
 - 1st column: base size = 100px, growth limit = 100px
 - 2nd column: base size = 20px, growth limit = 20px
 - 3rd column: base size = 20px, growth limit = 20px

And finally https://drafts.csswg.org/css-grid-2/#algo-flex-tracks expands the 3rd column to fill the 320px of the grid container:
 - 1st column: 100px
 - 2nd column: 20px
 - 3rd column: 200px





-- 
GitHub Notification of comment by Loirooriol
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10095#issuecomment-2004633083 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 18 March 2024 18:22:31 UTC