Closed Bug 1890562 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 45629 - Fix infinite loop in NearestMatchingAncestor

Categories

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

task

Tracking

()

RESOLVED FIXED
127 Branch
Tracking Status
firefox127 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Mason Freed <masonf@chromium.org> wrote:

Fix infinite loop in NearestMatchingAncestor

It was possible for an invoker/anchor to point back to itself
in a way that could cause an infinite loop. The new test case
exercises this path, and new DCHECKs make sure such a loop isn't
possible.

Fixed: 333424886
Change-Id: Ieb2cda38c5739d9faa4c1995ec43c04151273517
Reviewed-on: https://chromium-review.googlesource.com/5439715
WPT-Export-Revision: 3f03cea25bd1609f4b25d60d9db79029873adfa6

Component: web-platform-tests → DOM: Core & HTML
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
PASS : 1

Chrome

TIMEOUT: 1

Safari

OK : 1
PASS : 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

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