RE: EME At Risk Features


These aren’t candidates for editorial changes.  We pick them up now or don’t.

From: David Dorwin []
Sent: Thursday, June 9, 2016 4:24 PM
To: Jerry Smith (WPT) <>
Cc: Paul Cotton <>; Mark Watson ( <>; Matt Wolenetz <>;
Subject: Re: EME At Risk Features

Those are in different specs, so they can be made separately.

On Thu, Jun 9, 2016 at 4:20 PM, Jerry Smith (WPT) <<>> wrote:
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.


From: Paul Cotton
Sent: Wednesday, June 8, 2016 5:15 AM
To: Jerry Smith (WPT) <<>>
Cc: David Dorwin <<>>; Mark Watson (<>) <<>>; Matt Wolenetz <<>>;<>
Subject: RE: EME At Risk Features

I suggest the first two items be combined as “The "persistent-usage-record"<> session type and the related MediaKeySession destroyed<> algorithm.”


From: Jerry Smith (WPT)
Sent: Tuesday, June 7, 2016 4:49 PM
To: Paul Cotton <<>>
Cc: David Dorwin <<>>; Mark Watson (<>) <<>>; Matt Wolenetz <<>>
Subject: EME At Risk Features

The EME At Risk PR has been completed and merge.  It’s in the latest editor’s draft:

The following features are at risk and may be removed:

•         The "persistent-usage-record"<> session type.

•         The MediaKeySession destroyed<> algorithm.

•         Setting the media element's readyState<> value based on key availability in the Queue a "waitingforkey" Event<> and Attempt to Resume Playback If Necessary<> algorithms.

•         Support for insecure contexts, including the Are insecure contexts allowed?<> algorithm and steps that call it.
The first two of these are secure release.


Received on Thursday, 9 June 2016 23:30:16 UTC