Only inflate contenteditable blocks at the first fragment.

If a block is empty, it will usually fit inside one fragmentainer. But not always. If there's tall borders/padding, for instance, we might split the block into fragments. Never attempt to stretch the intrinsic block-size of a fragment unless we're working on the first one, or else we might end up creating an infinite number of them. Bug: 1261747 Change-Id: Ic9bc5c08259d39b39e3c7a5b6a49b197d1dd115a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3245260 Reviewed-by: Ian Kilpatrick <[email protected]> Commit-Queue: Morten Stenshorne <[email protected]> Cr-Commit-Position: refs/heads/main@{#935412}
Gabisampaio · Nov 18, 2021 · e186159 · e186159
1 parent 2775409
commit e186159
Showing 1 changed file with 7 additions and 0 deletions.
diff --git a/css/css-break/fragmented-empty-contenteditable-crash.html b/css/css-break/fragmented-empty-contenteditable-crash.html
@@ -0,0 +1,7 @@
+<!DOCTYPE html>
+<link rel="author" title="Morten Stenshorne" href="mailto:[email protected]">
+<link rel="help" href="https://bugs.chromium.org/p/chromium/issues/detail?id=1261747">
+<p>Test passes if it doesn't crash (or freeze).</p>
+<div style="columns:2; column-fill:auto; height:50px;">
+  <div style="padding-top:20px; padding-bottom:100px;" contenteditable="true"></div>
+</div>