Closed Bug 1821133 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 38892 - VT: Be resilient if there is no documentElement().

Categories

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

task

Tracking

()

RESOLVED FIXED
113 Branch
Tracking Status
firefox113 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(Depends on 1 open bug, )

Details

(Whiteboard: [wptsync downstream])

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

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

Vladimir Levin <vmpstr@chromium.org> wrote:

VT: Be resilient if there is no documentElement().

This patch updates all of the places where we access documentElement()
to make sure it either is there (via DCHECKs) or gate access
conditionally.

This is to address the referenced clusterfuzz. I can't repro this
locally, but it is clearly an access into a documentElement() when it's
null.

Since we can handle the null situations gracefully in all cases, this
is just an improvement to the robustness of the code.

R=khushalsagar@chromium.org

Bug: 1413903
Change-Id: I1b81e36a2b88291e364407241c3b0fd0c34de252
Reviewed-on: https://chromium-review.googlesource.com/4317782
WPT-Export-Revision: 4ff0022f077a9f4a78a05a9161add7f7d5890555

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 1 tests

Status Summary

Firefox

PASS : 1

Chrome

CRASH: 1

Safari

PASS : 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/049c1a1c5470 [wpt PR 38892] - VT: Be resilient if there is no documentElement()., a=testonly
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 113 Branch
You need to log in before you can comment on or make changes to this bug.