Update tests for forced breaks at fragmentainer start.
If there's a forced break, and it's at a valid class A breakpoint, we may break there. There's nothing in the spec suggesting otherwise. This is working correctly in the LayoutNG fragmentation engine, but not in the legacy engine (where we require some non-zero block-size content to allow forced breaks). Remove invalid tests, and add a couple of valid ones. Bug: 1100849 Change-Id: I1829a00a4e9761906ebe4536ded9c994f4737e69 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339663Reviewed-by:Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by:
Alison Maher <almaher@microsoft.com> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#795604}
Showing
Please register or sign in to comment