This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 25903 - [EME] Tighten up MediaKey Events definitions
Summary: [EME] Tighten up MediaKey Events definitions
Alias: None
Product: HTML WG
Classification: Unclassified
Component: Encrypted Media Extensions (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Mark Watson
QA Contact: HTML WG Bugzilla archive list
Depends on:
Reported: 2014-05-28 04:56 UTC by Chris Pearce
Modified: 2014-06-24 21:39 UTC (History)
5 users (show)

See Also:


Description Chris Pearce 2014-05-28 04:56:57 UTC
The spec for MediaKeyNeededEvent and MediaKeyMessageEvent definitions [1] should explicitly define a mapping from named entries in MediaKey*EventInit to MediaKey*Event.

i.e. it should be explicit what happens when script does this:

  var ev = new MediaKeyMessageEvent("something", {});

After that, what will ev.message be and why?

We also need to define what happens when parameters are empty; like in the example above, what's the default value of the initData? null presumably. And the other fields?

Also, we should define that the MediaKeyNeededEvent.initData and MediaKeyMessageEvent.message attributes are copied from their respective InitDict params during initialization. Otherwise if a reference to the InitDict's initData array is stored in the MediaKeyNeededEvent, other script could change the initData at any time, causing all kinds of problems.