Closed Bug 1754146 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 32741 - ComputedStyle may be null for disconnected elements

Categories

(Core :: DOM: CSS Object Model, task, P4)

task

Tracking

()

RESOLVED FIXED
99 Branch
Tracking Status
firefox99 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(Depends on 1 open bug, )

Details

(Whiteboard: [wptsync downstream])

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

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

Rune Lillesveen <futhark@chromium.org> wrote:

ComputedStyle may be null for disconnected elements

Should not use NOTREACHED() since it is a valid case to have null
ComputedStyle for elements which are not connected to a document.

Bug: 1291680
Change-Id: I901b68a004311d935fda2d46671b0c1d87c98e0b
Reviewed-on: https://chromium-review.googlesource.com/3443433
WPT-Export-Revision: 0ed948b9a607f6a9ec66a0aea00803990e951174

Component: web-platform-tests → DOM: CSS Object Model
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

PASS: 1

Safari

PASS: 1

Links

GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/7389b3bc2443 [wpt PR 32741] - ComputedStyle may be null for disconnected elements, a=testonly
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/421967a977d1 [wpt PR 32741] - ComputedStyle may be null for disconnected elements, a=testonly
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 99 Branch
You need to log in before you can comment on or make changes to this bug.