Closed Bug 1685363 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 27068 - content-visibility: Don't adjust position of a locked hittest result node.

Categories

(Core :: Layout, task, P4)

Product:
Core
Component:
Layout
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
86 Branch
Tracking Flags:
Tracking Status
firefox86 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

b'Vladimir Levin <vmpstr@chromium.org>' wrote:

content-visibility: Don't adjust position of a locked hittest result node.

This patch ensures that if we have a hittest result that has a locked
node, we don't try to recurse into its subtree. This can happen when we
do a PositionWithAffinity check.

R=chrishtr@chromium.org

Bug: 1162131
Change-Id: I357bd7032c6c2b6c9405bf26c49a36bda22d6a0d
Reviewed-on: https://chromium-review.googlesource.com/2611453
WPT-Export-Revision: 1904580f18ca4b11fdb92f24d68074633f02e728

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

CI Results

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

/css/css-contain/content-visibility/content-visibility-080.html
Caret range from point: FAIL (Chrome: FAIL, Safari: FAIL)

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/4cb7dbb242ab [wpt PR 27068] - content-visibility: Don't adjust position of a locked hittest result node., a=testonly https://hg.mozilla.org/integration/autoland/rev/9092fa5f1669 [wpt PR 27068] - Update wpt metadata, a=testonly

https://hg.mozilla.org/mozilla-central/rev/4cb7dbb242ab
https://hg.mozilla.org/mozilla-central/rev/9092fa5f1669

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