[LayoutNG] Fix bug with positioning fragmented oof elements
In cases where an oof element's static position was taken in a later fragmentainer than the start of its containing block, we would calculate the wrong start offset and starting fragmentainer for the oof. To fix this, instead of passing fragmentainer_consumed_block_size (which is the consumed column block size up to the column that the static position was taken in), update the containing_block_offset to be the offset from the start of the containing block to the root fragmentation context, as well as update the static position to be relative to this adjusted containing_block_offset. Bug: 1079031 Change-Id: I48c08e7debd291fa3acfa77af0bb6d242cedbbd3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2422213 Commit-Queue: Alison Maher <almaher@microsoft.com> Reviewed-by:Morten Stenshorne <mstensho@chromium.org> Reviewed-by:
Benjamin Beaudry <benjamin.beaudry@microsoft.com> Cr-Commit-Position: refs/heads/master@{#809917}
Showing
Please register or sign in to comment