Closed Bug 1950396 Opened 10 months ago Closed 10 months ago

[wpt-sync] Sync PR 50934 - scroll anchor: Use priority candidate as root for selection

Categories

(Core :: Layout: Scrolling and Overflow, task, P4)

task

Tracking

()

RESOLVED FIXED
137 Branch
Tracking Status
firefox137 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Vladimir Levin <vmpstr@chromium.org> wrote:

scroll anchor: Use priority candidate as root for selection

When an element is a priority candidate, then this
patch uses the element as a root for regular candidate
selection. This ensures that for large contenteditable content, we
still anchor to some child element instead of the whole editable box.

This is also consistent with the type of anchoring we would do
without focus.

R=flackr@chromium.org

Bug: 395489580
Change-Id: Id88477fc07cf0fbb82434e448a9f547314c3db6a

Reviewed-on: https://chromium-review.googlesource.com/6288047
WPT-Export-Revision: 3d4324a956abfb531174a334d14ad6ebaef9237d

Component: web-platform-tests → Layout: Scrolling and Overflow
Product: Testing → Core

CI Results

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

Total 1 tests and 1 subtests

Status Summary

Firefox

OK : 1
FAIL: 1

Chrome

OK : 1
FAIL: 1

Safari

OK : 1
FAIL: 1

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/9ad88bf49106 [wpt PR 50934] - scroll anchor: Use priority candidate as root for selection, a=testonly https://hg.mozilla.org/integration/autoland/rev/2a0e9fe48622 [wpt PR 50934] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 10 months ago
Resolution: --- → FIXED
Target Milestone: --- → 137 Branch
You need to log in before you can comment on or make changes to this bug.