commit 607df359743b5a9d91ef408f2f60ee365b8c6809
author Morten Stenshorne <mstensho@chromium.org> Fri Jul 01 19:16:50 2022
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> Fri Jul 01 19:16:50 2022
tree a652a6a4a5aec0e2acc80a4363fbdbb6d652ff53
parent f7cb99179e79f5f988afcb954d30ff8b5df0ea27

Pre-paint: OOF within monolithic content is contained normally.

If an out-of-flow fragment is contained within monolithic content, its
containing fragment is simply the parent fragment, just as if there's no
block fragmentation involved at all.

It's only when the containing block of the OOF participates in block
fragmentation, that things are special - the containing fragment is then
the nearest fragmentainer, not the fragment of the actual CSS containing
block.

Only set the new containing fragment when entering monolithic content;
keep the other info, such as fragmentainer index. The fragmentainer
index is needed in order to store a unique fragment ID in FragmentData
for the cloned fragments generated for repeated content, such as table
headers and footers during block fragmentation.

(cherry picked from commit 2640e32a0384bcec43c20691fdeabb82f8cd7058)

Bug: 1078927, 1336634, 1327969
Change-Id: Ie73a5328e6ccc65f2625742e3147b9a6af533769
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3714109
Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1016728}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3738328
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Auto-Submit: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/branch-heads/5060@{#1121}
Cr-Branched-From: b83393d0f4038aeaf67f970a024d8101df7348d1-refs/heads/main@{#1002911}