Closed Bug 1833516 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 40039 - [anchor-position] Fix anchor-scroll resolving name conflicts

Categories

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

task

Tracking

()

RESOLVED FIXED
115 Branch
Tracking Status
firefox115 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Xiaocheng Hu <xiaochengh@chromium.org> wrote:

[anchor-position] Fix anchor-scroll resolving name conflicts

anchor-scroll resolves anchor names with NGPhysicalAnchorQuery, which
however keeps only one of the anchors of the same name, causing
incorrect anchor-scroll behavior when there are name conflicts.

This patch makes NGPhysialAnchorQuery to keep the entire list of same
name anchors (like its logical counterpart), and then only propagate
the first one to NGLogicalAnchorQuery.

Fixed: 1441210
Change-Id: Ib85c651e2767ae27b316609917e207da32def2a2
Reviewed-on: https://chromium-review.googlesource.com/4529222
WPT-Export-Revision: 8e4ad4aad8e25170f5ec2f781f6e814dddadc92a

Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core

CI Results

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

Total 2 tests

Status Summary

Firefox

OK : 1
FAIL: 4

Chrome

OK : 1
PASS: 2
FAIL: 2

Safari

OK : 1
FAIL: 4

Links

Gecko CI (Treeherder)
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/36b91bba81a9 [wpt PR 40039] - [anchor-position] Fix anchor-scroll resolving name conflicts, a=testonly https://hg.mozilla.org/integration/autoland/rev/feb5bc4a9155 [wpt PR 40039] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 115 Branch
You need to log in before you can comment on or make changes to this bug.