Intent to Implement: EME: Make navigator.requestMediaKeySystemAccess() spec compliant
428 views
Skip to first unread message
John Rummell
unread,
Dec 5, 2016, 3:36:38 PM12/5/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to blin...@chromium.org
jrum...@chromium.orghttp://w3c.github.io/encrypted-media/
Require that one of 'audioCapabilities' and 'videoCapabilities' be specified in the configuration passed to navigator.requestMediaKeySystemAccess(), and require that the contentType strings used as part of the entries to 'audioCapabilities' and 'videoCapabilities' include the desired codec as part of the MIME type.
Currently Chrome allows configurations that don't include the fields listed to pass (provided the other parts of the configuration is supported). Missing codecs currently has a deprecation message, and one will be added for missing capabilities. The intent is that the non-compliant functionality will be removed in M58.
To be compliant with the current version of the EME specification.
Firefox: No public signals
Edge: Shipped
Safari: No public signals
Web developers: No signals
Edge appears to follow the spec. Firefox currently does not, possibly due to the W3C EME tests checking this incorrectly.This will improve compatibility between browsers. We are working with the Widevine team to include recommendations on the configurations passed to navigator.requestMediaKeySystemAccess() for their next client communication (scheduled for the start of January).
The second change is that the MIME types passed to videoCapabilities and audioCapabilities must have codecs specified. That already has a deprecation message since April.
Please correct me if it's more than that.
Regarding, "the W3C EME tests checking this incorrectly", have you fixed the test already?
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to John Rummell, Philip Jägenstedt, blink-dev
LGTM2
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
Dimitri Glazkov
unread,
Dec 13, 2016, 4:16:51 PM12/13/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Chris Harrelson, John Rummell, Philip Jägenstedt, blink-dev
LGTM3
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.