I thought about doing this yesterday, but elected to leave them separate. There is an outstanding request from @wolenetz to expand the at risk entry for TrackDefaults. If we want to pick that up, it would be simple to make this change too. I believe we need confirmation from you, Paul, before doing that. Jerry From: Paul Cotton Sent: Wednesday, June 8, 2016 5:15 AM To: Jerry Smith (WPT) <jdsmith@microsoft.com> Cc: David Dorwin <ddorwin@google.com>; Mark Watson (watsonm@netflix.com) <watsonm@netflix.com>; Matt Wolenetz <wolenetz@google.com>; public-hme-editors@w3.org Subject: RE: EME At Risk Features I suggest the first two items be combined as "The "persistent-usage-record"<https://w3c.github.io/encrypted-media/#idl-def-MediaKeySessionType.persistent-usage-record> session type and the related MediaKeySession destroyed<https://w3c.github.io/encrypted-media/#media-key-session-destroyed> algorithm." /paulc From: Jerry Smith (WPT) Sent: Tuesday, June 7, 2016 4:49 PM To: Paul Cotton <Paul.Cotton@microsoft.com<mailto:Paul.Cotton@microsoft.com>> Cc: David Dorwin <ddorwin@google.com<mailto:ddorwin@google.com>>; Mark Watson (watsonm@netflix.com<mailto:watsonm@netflix.com>) <watsonm@netflix.com<mailto:watsonm@netflix.com>>; Matt Wolenetz <wolenetz@google.com<mailto:wolenetz@google.com>> Subject: EME At Risk Features The EME At Risk PR has been completed and merge. It's in the latest editor's draft: https://w3c.github.io/encrypted-media/ The following features are at risk and may be removed: * The "persistent-usage-record"<https://w3c.github.io/encrypted-media/#idl-def-MediaKeySessionType.persistent-usage-record> session type. * The MediaKeySession destroyed<https://w3c.github.io/encrypted-media/#media-key-session-destroyed> algorithm. * Setting the media element's readyState<http://www.w3.org/TR/html5/embedded-content-0.html#dom-media-readystate> value based on key availability in the Queue a "waitingforkey" Event<https://w3c.github.io/encrypted-media/#queue-waitingforkey> and Attempt to Resume Playback If Necessary<https://w3c.github.io/encrypted-media/#resume-playback> algorithms. * Support for insecure contexts, including the Are insecure contexts allowed?<https://w3c.github.io/encrypted-media/#are-insecure-contexts-allowed---deprecated> algorithm and steps that call it. The first two of these are secure release. JerryReceived on Thursday, 9 June 2016 23:21:07 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:53:09 UTC