- From: <bugzilla@jessica.w3.org>
- Date: Tue, 16 Dec 2014 20:04:02 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25092 --- Comment #25 from David Dorwin <ddorwin@google.com> --- It seems that downscaling and "output-not-allowed" are alternative implementations for handling a key whose output requirements cannot be met. Applications should behave the same in both cases - do not fetch content that requires such a key. In the former, this wastes bandwidth and client resources. In the latter, playback will stop. In theory, we wouldn't even need to differentiate them because the "waiting for a key" logic would indicate a not-allowed key was used. If there is a preference for differentiating the two cases, I propose adding the following to MediaKeyStatus: "downscaled" - The key is not currently usable to decrypt media data at full quality (e.g. resolution) because its output requirements cannot currently be met. Media data decrypted with this key may be presented at a lower quality (in resolution or other factors). We can then add a non-normative note that applications should avoid using media data that uses keys whose status is "output-not-allowed" or "downscaled". -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 16 December 2014 20:04:04 UTC