[wpt-sync] Sync PR 42164 - May break before float, but still fit subsequent in-flow content.
Categories
(Core :: Layout, task, P4)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox120 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 42164 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/42164
Details from upstream follow.
Morten Stenshorne <mstensho@chromium.org> wrote:
May break before float, but still fit subsequent in-flow content.
It is possible for a float to be pushed to the next fragmentainer, while
still fitting subsequent in-flow content in the current fragmentainer.
Therefore, keep looking for content inside a culled inline, even if
we've found a float that belongs in a later fragmentainer.This is similar to how a float may be pushed below the current line if
it doesn't fit beside it, while still laying out items that come after
it DOM-tree-wise, on the same line. A float may be pushed to the next
fragmentainer if it doesn't fit in the current one. But there may still
be room for plenty of in-flow lines in the current fragmentainer.Bug: 1486411
Change-Id: Ic935dc9655d628ce33d2c5a0f20369ef5eba590f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4891619
Commit-Queue: Koji Ishii \<kojii@chromium.org>
Auto-Submit: Morten Stenshorne \<mstensho@chromium.org>
Reviewed-by: Koji Ishii \<kojii@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1201198}
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Comment 1•2 years ago
|
||
| Assignee | ||
Comment 2•2 years ago
|
||
CI Results
Ran 9 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 1 tests
Status Summary
Firefox
PASS: 1
Chrome
PASS: 1
Safari
PASS: 1
Links
Comment 4•2 years ago
|
||
| bugherder | ||
Description
•