Bug 1797036 [wpt PR 36616] - [anchor-position] Resolving inline containing blocks...
commit3b72f2668da6ebde0da02184f941db4fcf001a8d
authorKoji Ishii <kojii@chromium.org>
Thu, 10 Nov 2022 15:03:38 +0000 (10 15:03 +0000)
committermoz-wptsync-bot <wptsync@mozilla.com>
Fri, 11 Nov 2022 12:31:43 +0000 (11 12:31 +0000)
treea06f98f0fc94dd697f9d23fb9f20af533a72b1bd
parentd64b7e4047ec992bf233593aa8c71fa0de89a30b
Bug 1797036 [wpt PR 36616] - [anchor-position] Resolving inline containing blocks, a=testonly

Automatic update from web-platform-tests
[anchor-position] Resolving inline containing blocks

OOFs whose containing blocks are inline is another case where
the OOF fragments are not added to their containing blocks.

This patch utilizes the foundation for block fragmentation to
the case.

Bug: 1309178
Change-Id: I2e9c6d8320adc9b8ff7bcad871136b9663efbcf8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3974351
Reviewed-by: Kent Tamura <tkent@chromium.org>
Auto-Submit: Koji Ishii <kojii@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1063166}

--

wpt-commits: 9db869d55c710e6cd9ca1603d082c9c5da85cdb0
wpt-pr: 36616
testing/web-platform/tests/css/css-anchor-position/anchor-name-inline-001.html [new file with mode: 0644]