[wpt-sync] Sync PR 53657 - Block-in-inline: Stay in parallel flow, once established.
Categories
(Core :: Layout: Columns, task, P4)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox142 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 53657 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/53657
Details from upstream follow.
Morten Stenshorne <mstensho@chromium.org> wrote:
Block-in-inline: Stay in parallel flow, once established.
When a block has been overflowed, we normally establish a parallel
fragmentation flow for content inside it, but this is disabled if
preceded by a column spanner. If the column spanner is discovered "too"
late, we may have entered a parallel flow. Then stay in this parallel
flow even if a spanner is discovered, or else the outgoing break tokens
are lost. It could be that the inline layout algorithm ought to be
refactored to handle this better, but this is all thanks to
crbug.com/430249827 and is a situation that should never occur, so
probably not worth it.Also update a DCHECK, so that it makes the same exception for inline
break tokens as it already did for block break tokens.Bug: 364933065
Change-Id: I5051ca952f6247f691b956f68111a9d811158de7
Reviewed-on: https://chromium-review.googlesource.com/6714627
WPT-Export-Revision: 9fcbabb14db5391bb02f54afe6dc86dd8bda7bba
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 1•1 year ago
|
||
| Assignee | ||
Comment 2•1 year ago
|
||
CI Results
Ran 0 Firefox configurations based on mozilla-central, and Chrome, and Safari on GitHub CI
Total 2 tests
Status Summary
Chrome
PASS : 1
CRASH: 1
Safari
PASS : 2
Links
Comment 4•1 year ago
|
||
| bugherder | ||
Description
•