Closed
Bug 1459867
Opened 7 years ago
Closed 7 years ago
[wpt-sync] Sync PR 10887 - Verify sync XHR does not fire progress event
Categories
(Core :: DOM: Core & HTML, enhancement, P4)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla62
| Tracking | Status | |
|---|---|---|
| firefox62 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 10887 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/w3c/web-platform-tests/pull/10887
Details from upstream follow.
Adam Rice <ricea@chromium.org> wrote:
> Verify sync XHR does not fire progress event
>
> Sync XHR should not fire a "progress" event. Add a test to verify that
> it does not.
| Reporter | ||
Updated•7 years ago
|
Component: web-platform-tests → DOM
Product: Testing → Core
| Reporter | ||
Comment 1•7 years ago
|
||
| Reporter | ||
Comment 2•7 years ago
|
||
| Reporter | ||
Comment 3•7 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=d3974a8af2ae5404902f033a6279267bb4bc1387
| Reporter | ||
Comment 4•7 years ago
|
||
Ran 2 tests and 2 subtests
OK : 2
PASS : 1
FAIL : 1
New tests that have failures or other problems:
/xhr/sync-no-progress.any.worker.html
progress event should not be fired by sync XHR: FAIL
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/816d4ef0a3de
[wpt PR 10887] - Verify sync XHR does not fire progress event, a=testonly
https://hg.mozilla.org/integration/mozilla-inbound/rev/394a5ad2313c
[wpt PR 10887] - Update wpt metadata, a=testonly
Comment 6•7 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/816d4ef0a3de
https://hg.mozilla.org/mozilla-central/rev/394a5ad2313c
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox62:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla62
| Assignee | ||
Updated•7 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•