diff options
author | Oriol Brufau <obrufau@igalia.com> | 2025-05-14 13:35:49 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2025-05-14 20:35:49 +0000 |
commit | 1cceb5f6a09fedec81f925ba189fae102166cdd9 (patch) | |
tree | b1f9c1e83605a7fa66b1a0ecaa9eb22252fc2cf9 /tests/wpt/css-tests/css-transforms-1_dev/html/transform-matrix-001.htm | |
parent | 1499e2a87467a0f92462413e8f724407fac8bf40 (diff) | |
download | servo-main.tar.gz servo-main.zip |
Before this patch it wasn't possibly to simultaneously support intrinsic
min/max sizes and content alignment in the block axis. For example,
block containers only support the former, and flex containers only the
latter.
The reason is that the final block size was decided by the parent
formatting context *after* performing layout, while content alignment is
performed *during* layout.
To address the problem, this introduces the struct `LazySize`, which
contains the data to resolve the final size, except for the intrinsic
size. Thus the parent formatting context can first create a `LazySize`,
then pass it to the child layout so that (if necessary) it can compute
the final size once the intrinsic one is known, and after layout the
parent formatting context uses it to actually size the child.
This PR just provides the functionality that will be used by follow-ups,
but at this point no layout is using the `LazySize` provided by the
parent, so there shouldn't be any behavior change yet.
Testing: Unnecessary (no behavior change)
This is part of #36981 and #36982
Signed-off-by: Oriol Brufau <obrufau@igalia.com>
Diffstat (limited to 'tests/wpt/css-tests/css-transforms-1_dev/html/transform-matrix-001.htm')
0 files changed, 0 insertions, 0 deletions