Closed
Bug 1464957
Opened 6 years ago
Closed 6 years ago
[wpt-sync] Sync PR 11211 - [mediacapture] Simply test and use standard API
Categories
(Core :: Audio/Video: Recording, enhancement, P4)
Core
Audio/Video: Recording
Tracking
()
RESOLVED
FIXED
mozilla63
Tracking | Status | |
---|---|---|
firefox63 | --- | fixed |
People
(Reporter: mozilla.org, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 11211 into mozilla-central (this bug is closed when the sync is complete). PR: https://github.com/web-platform-tests/wpt/pull/11211 Details from upstream follow. Mike Pennisi <mike@mikepennisi.com> wrote: > [mediacapture] Simply test and use standard API > > The MediaStream's `active` event was removed from the specification in > December of 2015 [1]. The `addtrack` event offers similar semantics, and > as a standard API, it is expected to be implemented by all browsers > which follow the specification. In addition, because it does not depend > on media playback, its use allows `MediaElement#play` to be removed. > That removal simplifies the process of executing the test because > browsers are beginning to tighten their policies regarding automated > media playback [2]. > > [1] https://github.com/w3c/mediacapture-main/pull/291 > [2] https://developers.google.com/web/updates/2017/09/autoplay-policy-changes > > --- > > @yellowdoge @martinthomson @uysalere More context about autoplay is available [here](https://github.com/web-platform-tests/results-collection/pull/552). Other MediaCapture tests continue to rely on the `active` event and on automatic playback, but those definitely need a more advanced solution. Because a simpler solution seemed possible for this test, I thought I'd propose that first. Is there any reason to continue to us `onactive`?
Assignee | ||
Updated•6 years ago
|
Component: web-platform-tests → Audio/Video: Recording
Product: Testing → Core
Assignee | ||
Comment 1•6 years ago
|
||
Pushed to try https://treeherder.mozilla.org/#/jobs?repo=try&revision=6824957210e463b6ea189e05709f8aabf4e348e3
Assignee | ||
Comment 2•6 years ago
|
||
Pushed to try https://treeherder.mozilla.org/#/jobs?repo=try&revision=cb5e28cb32c1490450bb4f6e9eab9398dcda0ac9
Assignee | ||
Comment 3•6 years ago
|
||
Ran 1 tests and 6 subtests OK : 1 PASS : 3 FAIL : 3
Assignee | ||
Comment 4•6 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=29f85757f84362a7b7ef9b4708af618cb7e3de0f
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/57a276ab02e0 [wpt PR 11211] - [mediacapture] Simply test and use standard API, a=testonly
Pushed by archaeopteryx@coole-files.de: https://hg.mozilla.org/integration/mozilla-inbound/rev/f282d9917301 [wpt PR 11211] - [mediacapture] Simply test and use standard API, a=testonly
Comment 7•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/f282d9917301
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox63:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
You need to log in
before you can comment on or make changes to this bug.
Description
•