Closed Bug 1656092 Opened 4 years ago Closed 4 years ago

[wpt-sync] Sync PR 24805 - [FlexNG] Fix great-grandchild relative-position offsets.

Categories

(Core :: Layout: Flexbox, task, P4)

task

Tracking

()

RESOLVED FIXED
81 Branch
Tracking Status
firefox81 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Ian Kilpatrick <ikilpatrick@chromium.org> wrote:

[FlexNG] Fix great-grandchild relative-position offsets.

In order to determine the correct size to resolve %-based relative
top offsets against we need to determine if the available-size given
to a flex-item is definite.

Previously this worked as there was a bit on the LayoutBox which
captured this information. This patch for NG flex-items allows for
looking at the previous constraint space while outside of layout.

Bug: 1108508
Change-Id: I3104b7afd4d96b707a8110eb2ed5d59d17129580

Reviewed-on: https://chromium-review.googlesource.com/2327838
WPT-Export-Revision: 2174cb1f20f441c618c8c305337fcb87b5b23884

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

CI Results

Ran 6 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

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ccddfc0097df
[wpt PR 24805] - [FlexNG] Fix great-grandchild relative-position offsets., a=testonly
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 81 Branch
You need to log in before you can comment on or make changes to this bug.