- From: Oriol Brufau via GitHub <sysbot+gh@w3.org>
- Date: Thu, 11 Aug 2022 23:08:13 +0000
- To: public-css-archive@w3.org
Loirooriol has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-sizing] Last remembered size when fragmented? == https://drafts.csswg.org/css-sizing-4/#last-remembered > record the current inner dimensions of its [principal box](https://drafts.csswg.org/css-display-3/#principal-box) as its [last remembered size](https://drafts.csswg.org/css-sizing-4/#last-remembered). 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](https://drafts.csswg.org/resize-observer-1/#content-rect) and [border box](https://drafts.csswg.org/css-box-4/#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](https://webidl.spec.whatwg.org/#idl-frozen-array), which will correspond to the dimensions of the first column. A future version of this spec will extend the returned [FrozenArray](https://webidl.spec.whatwg.org/#idl-frozen-array) 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. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7598 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 11 August 2022 23:08:15 UTC