Skip to content

Commit

Permalink
[container-queries] Fix intrinsic-size invalidation for %-padding.
Browse files Browse the repository at this point in the history
%-padding in the block axis can also affect how the intrinsic-sizes
are calculated. We don't store what they resolve against, and miss the
cache when we have %-padding. Do this in the block-axis as well.

Fixed: 1281318
Change-Id: I7cf5ba9299ab6145adfbb225936d67cf9c387401
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4481154
Reviewed-by: David Grogan <dgrogan@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1137089}
  • Loading branch information
bfgeek authored and chromium-wpt-export-bot committed Apr 28, 2023
1 parent bf3a753 commit 37ae613
Showing 1 changed file with 1 addition and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@
"#container width 400px after padding is applied. #second is removed from the rendering");

// Reduce width by 1px to test that a re-layout is not stateful.
vertical.style.width = "399px";
vertical.style.width = "499px";

test(() => assert_equals(padded.offsetHeight, 100),
"#container height measured with 499px width. Both container children visible");
Expand Down

0 comments on commit 37ae613

Please sign in to comment.