GitLab

This doesn't make a lot of difference to the NG layout engine (except
that consumed block-size may now be larger than the block-size of the
preceding fragments combined). The reason for this change is so that
we'll write the correct offsets back to the legacy tree. This was wrong
for overflowing content whose containing block ended in an earlier
fragmentatainer, and that caused trouble for things like offsetTop.

This change requires us to replace some logic in the fieldset layout
algorithm that calculates the amount of space that a legend "eats" from
its containing fieldset. It's actually slightly simpler now. :)

Bug: 829028
Change-Id: I84c6188e61ee3e9eaff80f595935768fa68412bb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2429027
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Alison Maher <almaher@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#811630}