[css-sizing] Stretch-fitting inline size next to floats.
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- PR merge metrics
- PR metrics pending
Description
https://drafts.csswg.org/css-sizing-4/#stretch-fit-sizing
https://drafts.csswg.org/css-sizing-3/#auto-box-sizes
The spec currently doesn't provide a size keyword to achieve this effect, but there used to be one named "fill-available", then renamed to "fill", "stretch" and/or "stretch-fit".
The behavior is partially defined, though, in level 3.
"The size a box would take if its outer size filled the available space in the given axis; in other words, the stretch fit into the available space, if that is definite."
Furthermore, the spec already refers to stretch-fit sizing as part of resolving fit-content, so my question is: How is stretch-fitting in the inline dimension affected by adjacent floats?
<style>
.outerfloat { float:left; width:100px; height:100px; background:blue; }
.stf { overflow:hidden; width:fit-content; background:yellow; }
.spacer { float:left; width:300px; height:10px; }
</style>
<div style="width:500px;">
<div class="outerfloat"></div>
<div class="stf">
<div class="spacer"></div>
<div class="spacer"></div>
</div>
</div>
Should the yellow box fit to the right of the yellow box, or go below, and use the entire width of its containing block?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the CSS Sizing Level 4 stretch-fit sizing section and the Level 3 auto box sizes section, then analyze the supplied float and fit-content testcase. Determine whether the inline-size behavior places .stf beside .outerfloat or below it, and clarify the relevant specification wording once the behavior is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- frontend, web-dev
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100