Closed Bug 1928747 Opened 1 year ago Closed 1 year ago

[wpt-sync] Sync PR 48937 - Ensure XMLDocumentParser doesn't hit a nullptr isolate while parsing a fragment

Categories

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

task

Tracking

()

RESOLVED FIXED
134 Branch
Tracking Status
firefox134 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Nate Chapin <japhet@chromium.org> wrote:

Ensure XMLDocumentParser doesn't hit a nullptr isolate while parsing a fragment

Bug: 376320342
Change-Id: I32e153fd991088bf3a85c9977fcb0c4506713491

Reviewed-on: https://chromium-review.googlesource.com/5984010
WPT-Export-Revision: 47e4144db81bdb1125c9e362a467c835d4b2061a

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

PASS : 1

Chrome

CRASH: 1

Safari

PASS : 1

Links

GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/f9a708faaa45 [wpt PR 48937] - Ensure XMLDocumentParser doesn't hit a nullptr isolate while parsing a fragment, a=testonly
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 134 Branch
You need to log in before you can comment on or make changes to this bug.