forked from mirrors/gecko-dev
Automatic update from web-platform-tests Don't estimate the top of bottom-aligned OOFs as bottom. (This is a reland of https://chromium-review.googlesource.com/c/chromium/src/+/1355920 with proper rebaselining) We'll incorrectly think that we get fragmented in that case, which will lead to incorrect height, which will lead to incorrect top offset, which will lead to incorrect fragmentation. This has probably been the cause for a flaky web test, that behaved even worse in LayoutNG, because in NG we force legacy layout as soon as fragmentation is involved (so when entering printing, we typically need to rebuild the entire layout object tree, with no former height to base the bottom estimate on (which is what saved us when NG is disabled - ehm, at least most of the time)). TBR=atotic@chromium.org,eae@chromium.org Bug: 910300 Change-Id: I00bce89900c50d6db9b39a4b72dbd6ab653184a7 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng Reviewed-on: https://chromium-review.googlesource.com/c/1365436 Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#615089} -- wpt-commits: 97a0309c70736bfef4258336f63ae216e294d8d3 wpt-pr: 14436
8 lines
443 B
HTML
8 lines
443 B
HTML
<!DOCTYPE html>
|
|
<link rel="author" title="Morten Stenshorne" href="mailto:mstensho@chromium.org">
|
|
<style>
|
|
body { overflow:scroll; } /* Auto scrollbars may hide bugs. */
|
|
</style>
|
|
<p>There should be a green square below, and a smaller hotpink square.</p>
|
|
<div style="float:left; width:20px; height:20px; margin-top:80px; margin-right:30px; background:hotpink;"></div>
|
|
<div style="float:left; width:50px; height:50px; background:green;"></div>
|