1057891 - [EME] Resolve EME promises with void rather than undefined

Status: RESOLVED FIXED

(Core :: Audio/Video, defect)

Description

[Chris Pearce [:cpearce (Not reading bugmail)]]

As per https://www.w3.org/Bugs/Public/show_bug.cgi?id=26457 we should resolve EME promises with void, not undefined.

Comment 1

[Boris Zbarsky [:bzbarsky]]

It's the same thing.  The behavior is to resolve the promise with the JS undefined value.  The name for that value's type in IDL is "void".

Comment 2

[Chris Pearce [:cpearce (Not reading bugmail)]]

Ah. So we can remove the "// void, not any: https://www.w3.org/Bugs/Public/show_bug.cgi?id=26457" comments in MediaKeySession.webidl then?

Comment 3

[Boris Zbarsky [:bzbarsky]]

Yes, I believe so.  Those comments were marking me introducing a known deviation from the spec, with a link to the spec bug I filed in the process to get the spec to match my IDL.

Comment 4

[Chris Pearce [:cpearce (Not reading bugmail)]]

Now that Bug 26457 is resolved, we can remove those comments.

Comment 5

[Chris Pearce [:cpearce (Not reading bugmail)]]

Attachment: Patch

Comment 6

[Boris Zbarsky [:bzbarsky]]

Comment on attachment 8505866 [details] [diff] [review]
Patch

r=me

Comment 7

[Chris Pearce [:cpearce (Not reading bugmail)]]

https://hg.mozilla.org/integration/mozilla-inbound/rev/1c3062cfe741

Comment 8

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/mozilla-central/rev/1c3062cfe741

Comment 9

[Chris Pearce [:cpearce (Not reading bugmail)]]

Mass update firefox-status to track EME uplift.