w3c / w3c/csswg-drafts

[css-sizing] Last remembered size when fragmented?

Open
#7,598 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

css-sizing-4 Needs Edits
Dominant language
Bikeshed
Stars
4.9k
Forks
816
PR merge metrics
PR metrics pending

Description

https://drafts.csswg.org/css-sizing-4/#last-remembered

record the current inner dimensions of its principal box as its last remembered size.

What if the principal box is fragmented e.g. into different columns when inside a multicol container?

ResizeObserver only reports the size in the 1st column: https://drafts.csswg.org/resize-observer-1/#resize-observer-entry-interface

the current definitions of content rect and border box do not mention how those boxes are affected by multi-column layout. In this spec, there will only be a single ResizeObserverSize returned in the FrozenArray, which will correspond to the dimensions of the first column. A future version of this spec will extend the returned FrozenArray to contain the per-fragment size information.

So that's what Blink stores as the last remembered size.

Note that the last rememebred size is only used when the element has size containment, which makes it monolithic. So storing the sizes per fragment doesn't really make sense.

Just storing the size of the 1st fragment may be reasonable enough, but this should be clarified.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the CSS Sizing 4 section on the last remembered size and compare it with the Resize Observer definitions of content rect, border box, and fragment sizing. Determine how a fragmented principal box should be represented, then clarify the specification to state whether the first fragment or another size is used.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.