[wpt-sync] Sync PR 38892 - VT: Be resilient if there is no documentElement().
Categories
(Core :: CSS Parsing and Computation, task, P4)
Tracking
()
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.Bug: 1413903
Change-Id: I1b81e36a2b88291e364407241c3b0fd0c34de252
Reviewed-on: https://chromium-review.googlesource.com/4317782
WPT-Export-Revision: 4ff0022f077a9f4a78a05a9161add7f7d5890555
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 1•2 years ago
|
||
Assignee | ||
Comment 2•2 years ago
|
||
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
Comment 4•2 years ago
|
||
bugherder |
Description
•