Bug 21569 - Specify which Media Element behaviours may change with EME and which will not
Specify which Media Element behaviours may change with EME and which will not
Status: RESOLVED FIXED
Product: HTML WG
Classification: Unclassified
Component: Encrypted Media Extensions
unspecified
PC All
: P2 normal
: ---
Assigned To: Adrian Bateman [MSFT]
HTML WG Bugzilla archive list
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-04-03 15:15 UTC by Mark Watson
Modified: 2013-06-13 10:26 UTC (History)
7 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Watson 2013-04-03 15:15:42 UTC
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.