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 16612 - Consider wrapping all encrypted media methods inside a new interface
Summary: Consider wrapping all encrypted media methods inside a new interface
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: Encrypted Media Extensions (show other bugs)
Version: unspecified
Hardware: All All
: P1 normal
Target Milestone: ---
Assignee: David Dorwin
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on: 16613
Blocks: 17199
  Show dependency tree / graph
 
Reported: 2012-04-03 16:15 UTC by Mark Watson
Modified: 2012-08-17 05:58 UTC (History)
7 users (show)

See Also:

Attachments

Description Mark Watson 2012-04-03 16:15:19 UTC 
It has been suggested that only a single key manager attribute be added to the HTMLMediaElement itself in order to improve encapsulation. For example:

partial interface HTMLMediaElement {
    attribute MediaKeyManager keymanager;
};

interface MediaKeyManager {
  void generateKeyRequest(in DOMString keySystem, in Uint8Array? initData);
  void addKey(in DOMString keySystem, in Uint8Array key, in Uint8Array? initData, in DOMString? sessionId);
  void cancelKeyRequest(in DOMString keySystem, in DOMString? sessionId);
};
Comment 1 David Dorwin 2012-05-25 22:24:06 UTC 
Bug 16613 also relates to improving encapsulation. We should address these two issues together.

The Media Source Extensions effort is also discussing whether to encapsulate the methods - see bug 17082. We should track the progress there.
Comment 2 David Dorwin 2012-06-12 00:03:49 UTC 
Bug 16613 may address this for us. If we choose not to address that bug, then we will need to specifically address this one.
Comment 3 Yang Sun 2012-06-12 05:46:18 UTC 
Hi, Mark

So this is about encrypted key managed object for media element?
Will generateKeyRequest request browser or request web site?
Why no removeKey method for this interface?

KeySystem means encrypted mechinism used by this media element,right?
The generateKeyRequest will return a key to be used by addkey?

And what's the meaning of cancelKeyRequest? During requesting key from ??? and we cancel it by a button or js inside logic?

Sorry for so many questions.......

(In reply to comment #0)
> It has been suggested that only a single key manager attribute be added to the
> HTMLMediaElement itself in order to improve encapsulation. For example:
> 
> partial interface HTMLMediaElement {
>     attribute MediaKeyManager keymanager;
> };
> 
> interface MediaKeyManager {
>   void generateKeyRequest(in DOMString keySystem, in Uint8Array? initData);
>   void addKey(in DOMString keySystem, in Uint8Array key, in Uint8Array?
> initData, in DOMString? sessionId);
>   void cancelKeyRequest(in DOMString keySystem, in DOMString? sessionId);
> };
Comment 4 David Dorwin 2012-08-17 05:56:13 UTC 
Addressed by the object-oriented API (bug 16613).