Closed Bug 1797360 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 36653 - Ask the exclusion space if we have fragmented floats.

Categories

(Core :: Layout, task, P4)

task

Tracking

()

RESOLVED FIXED
108 Branch
Tracking Status
firefox108 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 36653 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/36653
Details from upstream follow.

Morten Stenshorne <mstensho@chromium.org> wrote:

Ask the exclusion space if we have fragmented floats.

It knows. But add a convenience method for it.

The has_float_break_inside_ flag in the fragment builder, on the other
hand, only worked for floats that were direct children of the formatting
context root.

Bug: 1377795
Change-Id: Ib819db1598845d3a0e0ef8f9a64a395280e54c1f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3977911
Reviewed-by: Ian Kilpatrick \<ikilpatrick@chromium.org>
Commit-Queue: Morten Stenshorne \<mstensho@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1063380}

Component: web-platform-tests → Layout
Product: Testing → Core

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

FAIL: 1

Safari

PASS: 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/6eea369c521c [wpt PR 36653] - Ask the exclusion space if we have fragmented floats., a=testonly
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 108 Branch
You need to log in before you can comment on or make changes to this bug.