[LayoutNG] Handle kOutOfFragmentainerSpace result types for OOFs
If we hit kOutOfFragmentainerSpace when laying out an OOF, add
it to the list of elements to continue in the next fragmentainer,
as if it had a break before.
Crash test added.
Bug: 1278350
Change-Id: Iddd9b97ef54e78e7605250da55a6dde687d5bd9a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3328442
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Alison Maher <almaher@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#950334}
diff --git a/css/css-break/large-text-node-oof-crash.html b/css/css-break/large-text-node-oof-crash.html
new file mode 100644
index 0000000..424d663
--- /dev/null
+++ b/css/css-break/large-text-node-oof-crash.html
@@ -0,0 +1,10 @@
+<!DOCTYPE html>
+<link rel="help" href="https://bugs.chromium.org/p/chromium/issues/detail?id=1278350">
+<div style="column-width: 0px;">
+ <div style="position: relative;">
+ <div></div>
+ <h1 style="column-width: 10px; position: absolute;">
+ uklgvffmyjpekennfouiqjxyxugvhqhrqpovcphzxfb
+ </h1>
+ </div>
+</div>
