fune/testing/web-platform/tests/css/css-layout-api/multicol-child-crash.https.html at 86ae9bb8ab4a840975f05aac8c1e4641e7c8bb15 - nagai/fune - Nagai Git

nagai/fune

forked from mirrors/gecko-dev

Morten Stenshorne 6c978413d8 Bug 1665633 [wpt PR 25598] - Treat NG objects inside legacy fragmentation as monolithic., a=testonly

Automatic update from web-platform-tests
Treat NG objects inside legacy fragmentation as monolithic.

And vice versa: Treat legacy objects as monolithic inside NG block
fragmentation.

The two block fragmentation implementations (NG and legacy) cannot
cooperate, so once we switch engine somewhere inside a fragmentation
context, we need to treat that subtree as monolithic.

This requires us to specify which fragmentation engine is being in use
when calling GetPaginationBreakability(), at least when possible at all.
This required some work in LayoutFlowThread and
LayoutMultiColumnFlowThread.

Bug: 1127112
Change-Id: I8e0c4d17fd8985c488614e01db23a0c63e899679
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2416069
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Frédéric Wang <fwang@igalia.com>
Cr-Commit-Position: refs/heads/master@{#808334}

--

wpt-commits: 7ff702657b4f55c2b84db189eb8fed8d3cc36797
wpt-pr: 25598

2020-09-23 09:03:04 +00:00

10 lines

317 B

HTML

Raw Blame History

 <!DOCTYPE html>
 <link rel="author" title="Morten Stenshorne" href="mailto:mstensho@chromium.org">
 <link rel="help" href="https://bugs.chromium.org/p/chromium/issues/detail?id=1127112#c9">
 <div style="columns:2;">
   <div style="display:layout(child-layout);">
     line1<br>
     line2<br>
     line3<br>
   </div>
 </div>