- From: <bugzilla@jessica.w3.org>
- Date: Mon, 28 Apr 2014 22:52:18 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25092 --- Comment #11 from Mark Watson <watsonm@netflix.com> --- (In reply to David Dorwin from comment #10) > I moved my proposal from comment #1 to bug 25409 since it addresses multiple > scenarios, including the subject of that bug. It could still be the solution > for this use case as well. I think the proposal of bug 25409 is a good one, but I don't think it adequately addresses this use-case. Requiring content that might be subject to restrictions such as downscaling to have a different key id, even a 'fake' one, is arbitrary and introduces a new system requirement (multiple key ids embedded in content) to address a limitation of a single platform (HTML). In general we should be able to play any and all content that is compatible with the byte-stream specification, including CENC for the ISO BMFF case. We should not introduce additional requirements on the byte-stream unless absolutely necessary. I'd be interested, though, in whether this is in fact an MSE requirement ? There could be other reasons why the UA might want to hint to the application that it should switch to a lower-resolution stream. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 28 April 2014 22:52:20 UTC