[wpt-sync] Sync PR 49807 - Block-in-inline shouldn't keep an IFC from being non-contiguous.
Categories
(Core :: Layout, task, P4)
Tracking
()
Tracking | Status | |
---|---|---|
firefox136 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
(Blocks 1 open bug, )
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 49807 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/49807
Details from upstream follow.
Morten Stenshorne <mstensho@chromium.org> wrote:
Block-in-inline shouldn't keep an IFC from being non-contiguous.
A block-in-inline may only contain fragmented parallel flows, for all we
know, so it cannot unconditionally count as "in-flow", since we might
fail to mark a container as potentially non-contiguous that way.In the test included, there's a text node "x xx", where the first word
should be in the first column, and the second word should be in the
fourth. There's no room for such a wide piece of text ("xx") before
we're past the tall float.Bug: 346876226
Change-Id: I5bcf8840a1c71783dfa0bdce442a92eb5ddbf7b4
Reviewed-on: https://chromium-review.googlesource.com/6108448
WPT-Export-Revision: 328b31b1530b04df541ba5674234d20323ae17eb
Assignee | ||
Updated•2 months ago
|
Assignee | ||
Comment 1•2 months ago
|
||
Assignee | ||
Comment 2•2 months 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
FAIL
: 1
Chrome
CRASH
: 1
Safari
PASS
: 1
Links
Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base
Details
New Tests That Don't Pass
- /css/css-break/block-in-inline-012.html [wpt.fyi]:
FAIL
(Chrome:CRASH
, Safari:PASS
)
https://hg.mozilla.org/mozilla-central/rev/f5ba44f35510
https://hg.mozilla.org/mozilla-central/rev/ffedb515dd8f
Description
•