19009 2012-09-25 15:34:22 +0000 A MediaKeys should belong to a single HTMLMediaElement. 2013-07-02 14:33:35 +0000 1 1 1 Unclassified HTML WG Encrypted Media Extensions unspecified All All RESOLVED FIXED P2 normal --- 19156 1 jer.noble adrianba ddorwin jer.noble mike public-html-media public-html-bugzilla oldest_to_newest 74438 0 jer.noble 2012-09-25 15:34:22 +0000 Typically, a DOM object has a single parent and 0-to-many child objects. When it is possible for a DOM Object to change parents (e.g. Node.appendChild(), TextTrack.addCue(), etc.) the new parent will first remove the child from it's existing parent. The normative section of HTMLMediaElement mediaKeys property should add a step to the effect of: "2. If the given /keys/ is already a HTMLMediaElement's /keys/, then remove the /keys/ from that HTMLMediaElement." 82927 1 jer.noble 2013-02-11 22:52:50 +0000 Ping. This is affecting implementation; the lifetime management issues implied by allowing MediaKeys to belong to multiple HTMLMediaElements are hairy. 84995 2 adrianba 2013-03-26 04:58:49 +0000 I don't think there's any reason why a single MediaKeys object couldn't be used with more than one media element. It is possible you might want to share keys, especially when we resolve bug 19208 so that we know how to keep playing if you already have the key information you need. This could be a quality of implementation issue. Media engines in user agents may support key sharing up to a certain number of elements (perhaps that limit is 1). It is likely that early implementations would do so after setting once but we shouldn't unnecessarily constrain future implementations. I propose that we update the spec to throw QUOTA_EXCEEDED exception or something similar if the limit has been reached. 84996 3 jer.noble 2013-03-26 05:17:32 +0000 (In reply to comment #2) > I don't think there's any reason why a single MediaKeys object couldn't be > used with more than one media element. It is possible you might want to > share keys, especially when we resolve bug 19208 so that we know how to keep > playing if you already have the key information you need. There's at least one good reason, listed above: it makes object lifetime management very hairy. This would be the first and only DOM object which can have multiple parents. > This could be a quality of implementation issue. Media engines in user > agents may support key sharing up to a certain number of elements (perhaps > that limit is 1). It is likely that early implementations would do so after > setting once but we shouldn't unnecessarily constrain future > implementations. I propose that we update the spec to throw QUOTA_EXCEEDED > exception or something similar if the limit has been reached. If you want MediaKeys objects to share keys, you should make that an explicit feature of the specification, rather than a side effect of a non-standard ownership model. 85010 4 jer.noble 2013-03-26 14:38:57 +0000 I retract the statement about MediaKeys being the first DOM object with multiple parents. MediaController also has multiple HTMLMediaElement parents. 85012 5 jer.noble 2013-03-26 15:27:29 +0000 Additionally, some CDMs will have to be implemented by the media element itself. (This is currently the case with the WebKit Mac port.) By requiring that a MediaKeys object be associated with multiple HTMLMediaElements simultaneously, it would make that implementation at best much more complicated and at worst impossible. The benefit posed (sharing keys between media elements) is entirely speculative and could be achieved simply by adding the same key to two, separate MediaKeys objects. 86602 6 adrianba 2013-04-23 18:56:23 +0000 We discussed this on the telcon: http://www.w3.org/2013/04/02-html-media-minutes.html#item01 86719 7 adrianba 2013-04-24 20:54:32 +0000 Discussed in the F2F. Next steps: 1) Add a step that throws an exception from setMediaKeys if the media element would exceed the user agent's ability to share the MediaKeys object. 2) Add a note to the spec that explains that MediaKeys and MediaKeySession may not be functional in some implementations until the MediaKeys object is set to a media element. 87059 8 ddorwin 2013-05-01 03:19:20 +0000 Consider the related use case in bug 19156 as well. The above resolution may be sufficient. 90110 9 adrianba 2013-07-02 14:33:35 +0000 Changeset -> https://dvcs.w3.org/hg/html-media/rev/f4d8dc9bdacc