Closed Bug 1803707 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 37289 - [popover][anchor-position] Implement `anchor-scroll: implicit`

Categories

(Core :: DOM: Core & HTML, task, P4)

Product:
Core
Component:
DOM: Core & HTML
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
109 Branch
Tracking Flags:
Tracking Status
firefox109 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Xiaocheng Hu <xiaochengh@chromium.org> wrote:

[popover][anchor-position] Implement anchor-scroll: implicit

This patch implements the 'implicit' keyword for the 'anchor-scroll'
property, so that a popover using implicit anchoring can move with the
anchor during scrolling.

Bug: 1307772, 1380112
Change-Id: I70ccc3dd75666f1f49e01a93afad9d4e38247c6a
Reviewed-on: https://chromium-review.googlesource.com/4074664
WPT-Export-Revision: 4c3b10e8cb558912ef7ae54281438d235959a2a7

Component: web-platform-tests → DOM: Core & HTML
Product: Testing → Core

CI Results

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

Total 1 tests

Status Summary

Firefox

TIMEOUT: 1

Chrome

FAIL : 1

Safari

TIMEOUT: 1

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/b06bd4c3a97d [wpt PR 37289] - [popover][anchor-position] Implement `anchor-scroll: implicit`, a=testonly https://hg.mozilla.org/integration/autoland/rev/e55822d005a8 [wpt PR 37289] - Update wpt metadata, a=testonly

https://hg.mozilla.org/mozilla-central/rev/b06bd4c3a97d
https://hg.mozilla.org/mozilla-central/rev/e55822d005a8

Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox109: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 109 Branch
You need to log in before you can comment on or make changes to this bug.