[Bug 25092] Need a way to inform script that resolution restrictions are applied

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25092

--- Comment #26 from Joe Steele <steele@adobe.com> ---
(In reply to David Dorwin from comment #25)
> 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".

I am reaching out internally for more context here, but my gut feeling is that
we would want to differentiate. 

My thinking is that we will have applications that work in environments that do
not support downscaling. In that case the "downscaled" status would tell the
app to get a lower res stream, while the "output-not-allowed" status would tell
the app to display an error message, possibly indicating to the user how they
can correct the problem.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 12 January 2015 21:43:13 UTC