Closed Bug 1474039 Opened 6 years ago Closed 6 years ago

[wpt-sync] Sync PR 11832 - Update the media-capabilities IDL file

Categories

(Testing :: web-platform-tests, enhancement, P4)

enhancement

Tracking

(firefox63 fixed)

RESOLVED FIXED
mozilla63
Tracking Status
firefox63 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

 wrote:
>  Update the media-capabilities IDL file
>  
>  Hello reviewer(s),
>  
>  This PR is intended to consolidate the spec’s IDL definition with the WPT test suite’s copy, and any idlharness tests.
>  
>  The up-to-date copy of the IDL file was automatically extracted from the reffy-reports repo (https://github.com/tidoust/reffy-reports/tree/master/whatwg/idl) which scrapes known specs automatically + regulary.
>  
>  This PR is part of a migration project which will eventually be automatically updating and creating PRs for changes in spec IDL.
>  
>  Please check that:
>  The spec (and its source) is correct and up-to-date
>  All tests which cover the IDL in the spec have been migrated to fetch + use the idl in the interfaces/ directory (instead of inline copies in the test files).
>  
>  There are 18 test failures I am getting, but these existed before this update.
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
The PR was not expected to affect any tests, but the try push wasn't a success. Check the try results for infrastructure issues
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/e3ee5542412c
[wpt PR 11832] - Update the media-capabilities IDL file, a=testonly
https://hg.mozilla.org/mozilla-central/rev/e3ee5542412c
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
You need to log in before you can comment on or make changes to this bug.