Open
Bug 1016711
Opened 10 years ago
Updated 2 years ago
[EME] Clean up MediaKeyError
Categories
(Core :: Audio/Video: Playback, defect, P3)
Tracking
()
NEW
People
(Reporter: cpearce, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 obsolete file)
MediaKeyError isn't specified stably in the EME spec. It subclasses DOMException, and bz doesn't like that:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25896
The spec author aren't even sure they want a MediaKeyError event/object:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21798
So we need to clean up MediaKeyError once the spec stabilizes here.
| Comment hidden (obsolete) |
| Comment hidden (obsolete) |
|
Reporter | |
Updated•10 years ago
|
Assignee: cpearce → nobody
|
||
Comment 3•10 years ago
|
||
These bugs are fit and finish issues that might block EME uplift to Aurora.
Blocks: eme-m3
|
|
||
Comment 4•10 years ago
|
||
Chris, is this MediaKeyError bug still relevant? Does it need to block the adobe-eme release?
Flags: needinfo?(cpearce)
|
|
Reporter | |
Comment 5•10 years ago
|
||
Yes. Partners require a way to report keysystem specific errors.
There's a proposal in https://www.w3.org/Bugs/Public/show_bug.cgi?id=26776 that looks quite similar to what we have implemented.
Flags: needinfo?(cpearce)
|
||
Updated•9 years ago
|
Component: Audio/Video → Audio/Video: Playback
Mass change P2 -> P3
Priority: P2 → P3
|
|
Reporter | |
Comment 8•8 years ago
|
||
It looks like Chromium removed this in Feb 2016:
https://chromium.googlesource.com/chromium/src.git/+/fdb9a2bea13a877eef407fe7359b056b56d8ab2e
https://bugs.chromium.org/p/chromium/issues/detail?id=249976
|
|
Reporter | |
Comment 9•8 years ago
|
||
One thing to consider when I get back to this; should the legacy CDM error translate into an "error" being dispatched to the HTMLMediaElement?
|
||
Comment 11•6 years ago
|
||
No assignee, updating the status.
|
|
||
Comment 12•6 years ago
|
||
No assignee, updating the status.
|
|
||
Comment 13•6 years ago
|
||
No assignee, updating the status.
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•