- From: <bugzilla@jessica.w3.org>
- Date: Thu, 22 May 2014 17:26:10 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25866 Bug ID: 25866 Summary: "needkey" event name is misleading Product: HTML WG Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P3 Component: Encrypted Media Extensions Assignee: adrianba@microsoft.com Reporter: ddorwin@google.com QA Contact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-media@w3.org The "needkey" event was originally intended to indicate "this stream is (may be) encrypted" and provide some data about it. At one time, it was even possible to fire in response to not having the key for a block. Since then, the algorithm has changed, we've dropped MEDIA_ERR_ENCRYPTED, and put less focus on using this event to drive createSession() calls. The event that is fired Initialization Data Encountered [1] does not necessarily mean that a key is needed (only the CDM knows this and the CDM is not involved in firing this event). Therefore, I think we should rename it to avoid confusion. Since the event is fired at HTMLMediaElement, it should somehow indicate that it is related to EME/encrypted content. For example, "initdata" is too general and ambiguous. Possible options include "encrypted" and "encryptedinitdata". [1] https://dvcs.w3.org/hg/html-media/raw-file/default/encrypted-media/encrypted-media.html#algorithms-initdata-encountered -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 22 May 2014 17:26:15 UTC