Closed
Bug 1874493
Opened 1 year ago
Closed 1 year ago
[wpt-sync] Sync PR 43979 - [testdriver] Detect testharness context lazily
Categories
(Testing :: web-platform-tests, task, P4)
Testing
web-platform-tests
Tracking
(firefox123 fixed)
RESOLVED
FIXED
123 Branch
Tracking | Status | |
---|---|---|
firefox123 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 43979 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/43979
Details from upstream follow.
Jonathan Lee <jonathanjlee@google.com> wrote:
[testdriver] Detect testharness context lazily
Currently, loading testdriver.js before testharness.js causes testdriver.js to think it's in a non-testharness context even after testharness.js is loaded. To reduce surprises for test authors, defer evaluation of
is_test_context
to when actions actually need to be created or handled.See Also: https://crbug.com/1517740
Assignee | ||
Comment 1•1 year ago
|
||
Assignee | ||
Comment 2•1 year ago
|
||
The PR was not expected to affect any tests, but the try push wasn't a success. Check the try results for infrastructure issues
Assignee | ||
Comment 3•1 year ago
|
||
Test result changes from PR not available.
Assignee | ||
Comment 4•1 year ago
|
||
Test result changes from PR not available.
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b7f778a25077
[wpt PR 43979] - [testdriver] Detect testharness context lazily, a=testonly
Comment 6•1 year ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox123:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 123 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•