Treat NG objects inside legacy fragmentation as monolithic.

mstensho · chromium-wpt-export-bot · commit 7ff702657b4f · 2020-09-18T08:03:51.000-07:00
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}
diff --git a/css/css-layout-api/multicol-child-crash.https.html b/css/css-layout-api/multicol-child-crash.https.html
@@ -0,0 +1,10 @@
+<!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>
