[css-flexbox-1] Clarify point 9.2(4) in the flexbox algorithm #11438

gitspeaks · 2025-01-04T16:25:21Z

Is point 9.2(4) essentially a goto 9.2(2) after the main sizes of the flex items have been determined, in order to use those combined measurements as the definitive flex container main size and restart the algorithm assuming definite free space?

Example:

<!DOCTYPE html>
<html>
<head>
<style>
  body,
  html {
    height: 100%;
    margin: 0;
  }
  .flex {
    display: flex;
    flex-flow: row nowrap;
    width: max-content;
    background: red;    
  }
  .flex > div {
    background: green;        
    flex-basis: 50%;
  }
</style>
</head>
<body>
  <div class="flex">
    <div>1234 56789</div>
  </div>
</body>
</html>

output:

Here the flex container's size is indefinite. According to the flex-basis percentage sizing rule, the algorithm calculates the base size of the flex item using the same constraint set on the container — max-content.

The question is: once this calculation is complete, does point 9.2(4) instruct the algorithm to restart, using the measured main size of the child <div> as the flex container's definitive main size? If so, would the child <div>'s main size be recalculated using 50% of the flex container's now definite main size (effectively 50% of the child's previously determined max-content size)?

The text was updated successfully, but these errors were encountered:

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[css-flexbox-1] Clarify point 9.2(4) in the flexbox algorithm #11438

[css-flexbox-1] Clarify point 9.2(4) in the flexbox algorithm #11438

gitspeaks commented Jan 4, 2025

[css-flexbox-1] Clarify point 9.2(4) in the flexbox algorithm #11438

[css-flexbox-1] Clarify point 9.2(4) in the flexbox algorithm #11438

Comments

gitspeaks commented Jan 4, 2025