- From: <bugzilla@jessica.w3.org>
- Date: Tue, 05 Nov 2013 02:04:22 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21203
David Dorwin <ddorwin@google.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
--- Comment #29 from David Dorwin <ddorwin@google.com> ---
One of the original changesets for this bug
(https://dvcs.w3.org/hg/html-media/rev/69dbfb8baca8) introduced a second
instance of reporting MEDIA_ERR_ENCRYPTED. This one was introduced in 4.1 First
Time a Key Reference is Encountered when needkey is to be fired but media data
is not CORS-same-origin. Previously, the error could only be reported when a
key was actually needed in 4.2. Encrypted Block Encountered.
Should we really report an error when the first key reference is encountered or
should we wait until an encrypted block is encountered (even though we cannot
report a needkey event). It's possible playback could proceed without error
(i.e. using only unencrypted streams within the media data. Also, having one
place to report errors is simpler for impelementors.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 5 November 2013 02:04:24 UTC