https://www.w3.org/Bugs/Public/show_bug.cgi?id=19809
Priority: P3
Bug ID: 19809
CC: mike@w3.org, public-html-media@w3.org
Assignee: adrianba@microsoft.com
Summary: Specify which portion of addKey() algorithm to run
when updating license for a key
QA Contact: public-html-bugzilla@w3.org
Severity: normal
Classification: Unclassified
OS: All
Reporter: ddorwin@google.com
Hardware: All
Status: NEW
Version: unspecified
Component: Encrypted Media Extensions
Product: HTML WG
http://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/encrypted-media.html#dom-addkey
describes the behavior "For each individual key in |key|". This would seem to
mean any time |key| includes a key, these operations should be performed, even
if the CDM already had a specific key.
Questions:
#1 If a new license (i.e. renewal, update, policy change) is received with the
same |key|, should those operations be performed?
#2 If so, should we say "For each individual key _represented_ in |key|" since
these subsequent licenses may not actually specify the key itself again?
The most debatable issue might be whether to fire keyadded in this case. It
probably makes sense to always "attempt to resume playback" because it's
possible that the new license will allow previously stalled playback to resume.
--
You are receiving this mail because:
You are the QA Contact for the bug.