Bug 1768171 [wpt PR 33964] - Ignore forced breaks in OOFs during initial column balan...
commit3955d2d894b63fb205f6cf27395e3ddd77aab326
authorMorten Stenshorne <mstensho@chromium.org>
Mon, 16 May 2022 10:05:35 +0000 (16 10:05 +0000)
committermoz-wptsync-bot <wptsync@mozilla.com>
Tue, 17 May 2022 16:14:27 +0000 (17 16:14 +0000)
tree99bf4f7c7c97f76b0c1726b0157b8a0b835322fe
parente3df5ebb5eb7bc1ea00243e1a061d8c4a1575909
Bug 1768171 [wpt PR 33964] - Ignore forced breaks in OOFs during initial column balancing., a=testonly

Automatic update from web-platform-tests
Ignore forced breaks in OOFs during initial column balancing.

The main layout machinery doesn't support resuming after breaks inside
OOFs. We rely on special-code in NGOutOfFlowLayoutPart and
NGSimplifiedOOFLayoutAlgorithm invoked at the outermost fragmentation
context root for this to work.  However, during initial column
balancing, we don't treat OOFs specially, but this isn't implemented for
the main machinery.

To fix this correctly, we would have to store the incoming break token
for an OOF in NGPhysicalOutOfFlowPositionedNode and do some more stuff
in NGOutOfFlowLayoutPart. But I don't think it's necessary at this
point, so just make sure that we never break inside OOFs in the initial
column balancing pass.

Bug: 1322319
Change-Id: I062a0ca2f57d24bd877a74e20cdb70dcff33ad20
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3629358
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Alison Maher <almaher@microsoft.com>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1000918}

--

wpt-commits: d09850ce75db0e9b0fde8e1e27d102faab0091e7
wpt-pr: 33964
testing/web-platform/tests/css/css-multicol/crashtests/forced-break-in-oof-in-column-balancing-nested.html [new file with mode: 0644]
testing/web-platform/tests/css/css-multicol/crashtests/forced-break-in-oof-in-column-balancing.html [new file with mode: 0644]