Closed
Bug 1180482
Opened 9 years ago
Closed 8 years ago
[EME] navigator.requestMediaKeySystemAccess supportedConfigurations parameter should not be optional
Categories
(Core :: Audio/Video: Playback, defect, P3)
Core
Audio/Video: Playback
Tracking
()
People
(Reporter: sjakthol, Unassigned)
References
(Blocks 1 open bug, )
Details
STR:
1. Execute the following in the web console: navigator.requestMediaKeySystemAccess('org.w3.clearkey')
Expected results: The returned promise is rejected with a TypeError.
Actual results: The promise is fulfilled with a MediaKeySystemAccess object.
Chrome handles this according to the spec.
For details, see:
https://w3c.github.io/encrypted-media/#requestMediaKeySystemAccess
https://github.com/w3c/encrypted-media/issues/1
Comment 1•9 years ago
|
||
Thanks, Sami!
status-firefox39:
--- → affected
status-firefox40:
--- → affected
status-firefox41:
--- → affected
status-firefox42:
--- → affected
Component: Audio/Video → Audio/Video: Playback
Priority: -- → P2
Summary: [EME] Navigator.requestMediaKeySystemAccess supportedConfigurations parameter should not be optional → [EME] navigator.requestMediaKeySystemAccess supportedConfigurations parameter should not be optional
Mass change P2 -> P3
Priority: P2 → P3
Comment 3•8 years ago
|
||
Can be handled in the navigator.requestMediaKeySystemAccess() refactorings I'm doing as part of bug 1274338.
Depends on: 1274338
Comment 4•8 years ago
|
||
(In reply to Chris Pearce (:cpearce) from comment #3)
> Can be handled in the navigator.requestMediaKeySystemAccess() refactorings
> I'm doing as part of bug 1274338.
I meant bug 1278198.
Comment 5•8 years ago
|
||
Should be fixed in tomorrow's Nightly build onwards. Fixed by bug 1278198.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•