This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The spec currently adds a new |keySystem| attribute to HTMLSourceElement such that it can be used in selecting the correct source. For example: <source keySystem="com.example.somesystem" type="video/webm"> Currently, the source is selected but the keySystem is not. This is inconsistent and doesn't provide any way for the application to detect which keySystem was used in selecting the source. (In the original spec, keySystem was an attribute on the HTMLMediaElement. I propose that when a <source> with a |keySystem| is selected, a new MediaKeys object should be created for |keySystem| and be assigned to the HTMLMediaElement's |keys| attribute. This is the equivalent of "video.src = new MediaKeys(keySystem);". This also ensures that <source> use is consistent with the best practices added in https://www.w3.org/Bugs/Public/show_bug.cgi?id=19156#c9. (Another option is to revisit the decision not to revert the addition of |keySystem| in bug 20336.)
(In reply to David Dorwin from comment #0) > The spec currently adds a new |keySystem| attribute to HTMLSourceElement > such that it can be used in selecting the correct source. For example: > <source keySystem="com.example.somesystem" type="video/webm"> No, it doesn't. As far as I can tell, there is nothing in the EME spec that'd add a markup attribute to the <source> element. It just adds a DOM attribute. (A markup attribute couldn't be in the camel case anyway.)
(In reply to Henri Sivonen from comment #1) > (In reply to David Dorwin from comment #0) > > The spec currently adds a new |keySystem| attribute to HTMLSourceElement > > such that it can be used in selecting the correct source. For example: > > <source keySystem="com.example.somesystem" type="video/webm"> > > No, it doesn't. As far as I can tell, there is nothing in the EME spec > that'd add a markup attribute to the <source> element. It just adds a DOM > attribute. (A markup attribute couldn't be in the camel case anyway.) That was the intent. Thanks for pointing this out. I filed bug 23897 to fix this.
I believe we should consider removing the keySystem from HTMLSourceElement. It has the issue noted by David, but also doesn't seem to fit well with a significant use case. The source element is most useful for sites that want to provide media options in HTML for automatic consumption by HTMLMediaElements. Since EME requires JS implementations anyway, it seems unlikely that sites will need to use the source element to align media formats and keySystems with ones supported by the UA.
I reopened bug 20336. We can close this as obsolete if we address that bug.
HTMLSourceElement has been removed (bug 20336), making this bug obsolete.