- From: <bugzilla@jessica.w3.org>
- Date: Wed, 03 Apr 2013 15:15:42 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21569 Bug ID: 21569 Summary: Specify which Media Element behaviours may change with EME and which will not Classification: Unclassified Product: HTML WG Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: Encrypted Media Extensions Assignee: adrianba@microsoft.com Reporter: watsonm@netflix.com QA Contact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-media@w3.org https://www.w3.org/Bugs/Public/show_bug.cgi?id=21155 already points out that APIs that allow access to decoded media may not behave in the same way with encrypted media. We should specify whether there are other changes and where there shall not be changes. For example http://lists.w3.org/Archives/Public/public-restrictedmedia/2013Apr/0001.html asks whether synchronization between tracks will still be provided in the same way (of course it should be). Also, it is possible that with hardware media pipelines, CSS transforms may not be fully supported - the media element may be restricted to occupying a rectangular region with top and sides parallel to the top and sides of the screen, respectively. It seems possible that scaling of the video image away from its normal aspect ratio (stretching) may also not be supported. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 3 April 2013 15:15:46 UTC