Closed
Bug 1515866
Opened 5 years ago
Closed 5 years ago
[wpt-sync] Sync PR 14624 - Don't create a logging output element until we have DOMContentLoaded
Categories
(Testing :: web-platform-tests, enhancement, P4)
Testing
web-platform-tests
Tracking
(firefox67 fixed)
RESOLVED
FIXED
mozilla67
Tracking | Status | |
---|---|---|
firefox67 | --- | fixed |
People
(Reporter: mozilla.org, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 14624 into mozilla-central (this bug is closed when the sync is complete). PR: https://github.com/web-platform-tests/wpt/pull/14624 Details from upstream follow. James Graham <james@hoppipolla.co.uk> wrote: > Don't create a logging output element until we have DOMContentLoaded > > Otherwise running with logs enabled can implicitly create a > document.body that can change the results of tests.
Assignee | ||
Comment 1•5 years ago
|
||
Pushed to try https://treeherder.mozilla.org/#/jobs?repo=try&revision=21bcdfa002b2aff74327b1e580848249e5f6eca3
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/faddcb80fe38 [wpt PR 14624] - Don't create a logging output element until we have DOMContentLoaded, a=testonly
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/7bffd692126e [wpt PR 14624] - Don't create a logging output element until we have DOMContentLoaded, a=testonly
Comment 4•5 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox67:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
You need to log in
before you can comment on or make changes to this bug.
Description
•