1840976 - [wpt-sync] Sync PR 40800 - [anchor-position] Implement 'position-fallback-bounds'

Status: RESOLVED FIXED

(Core :: CSS Parsing and Computation, task, P4)

Description

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

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

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

Xiaocheng Hu <[e-mail]> wrote:

[anchor-position] Implement 'position-fallback-bounds'

This patch implements the 'position-fallback-bounds' property by:
(1) Also checking the additional fallback-bounds rect in
NGOutOfFlowLayoutParts::CalculateOffset()
(2) Also keep track of the scroll offset of the additional bounds rect
in AnchorScrollData, and use that as an input (1)
(3) Augments the existing non-overflowing scroll range structure with
an additional range (see the NonOverflowingScrollRange struct) to
help determine whether the additional fallback-bounds rect is
overflown.

Spec: https://drafts.csswg.org/css-anchor-position-1/#fallback-bounds

Bug: 1455557
Change-Id: I60cd8c22e84d5d70d7f1f73258aa8d60c30480f4
Reviewed-on: https://chromium-review.googlesource.com/4655384
WPT-Export-Revision: 44c1f1ab18f18f04b946a03b1e1757ebe36076cd

Comment 1

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=392cd25db2625b3fee1b410e32285e72b7d37f1b

Comment 2

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

CI Results

Ran 9 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 5 tests and 3 subtests

Status Summary

Firefox

OK : 5
FAIL: 14

Chrome

OK : 5
PASS: 5
FAIL: 9

Safari

OK : 5
FAIL: 14

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

• /css/css-anchor-position/position-fallback-bounds-001.html [wpt.fyi]
  • .target 1: FAIL (Chrome: FAIL, Safari: FAIL)
  • .target 2: FAIL (Chrome: FAIL, Safari: FAIL)
• /css/css-anchor-position/position-fallback-bounds-002.html [wpt.fyi]
  • .target 1: FAIL (Chrome: FAIL, Safari: FAIL)
  • .target 2: FAIL (Chrome: FAIL, Safari: FAIL)
• /css/css-anchor-position/position-fallback-bounds-003.html [wpt.fyi]
  • Target is at anchor's top-left corner at initial scroll position: FAIL (Chrome: PASS, Safari: FAIL)
  • Target falls back to anchor's bottom-left corner after anchor is scrolled upwards: FAIL (Chrome: FAIL, Safari: FAIL)
  • Target falls back to anchor's bottom-right corner after anchor is further scrolled leftwards: FAIL (Chrome: FAIL, Safari: FAIL)
  • Target falls back to anchor's top-left corner after anchor is scrolled back downwards: FAIL (Chrome: FAIL, Safari: FAIL)
• /css/css-anchor-position/position-fallback-bounds-004.html [wpt.fyi]
  • Target is above anchor at initial scroll position: FAIL (Chrome: PASS, Safari: FAIL)
  • Target falls back to below anchor after anchor is scrolled upwards: FAIL (Chrome: FAIL, Safari: FAIL)
  • Target returns to above anchor after bounds are scrolled upwards: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-anchor-position/position-fallback-bounds-005.html [wpt.fyi]
  • Initial layout: FAIL (Chrome: PASS, Safari: FAIL)
  • Layout is updated after position-fallback-bounds property changes: FAIL (Chrome: FAIL, Safari: FAIL)
  • Layout is updated after additional fallback-bounds rect changes: FAIL (Chrome: PASS, Safari: FAIL)

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/8fa0d254b1f7
[wpt PR 40800] - [anchor-position] Implement 'position-fallback-bounds', a=testonly
https://hg.mozilla.org/integration/autoland/rev/7f6c75fa5f8a
[wpt PR 40800] - Update wpt metadata, a=testonly

Comment 4

[Iulian Moraru]

https://hg.mozilla.org/mozilla-central/rev/8fa0d254b1f7
https://hg.mozilla.org/mozilla-central/rev/7f6c75fa5f8a