Steps to reproduce
See this test case:
Click anywhere on the canvas to run getImageData. If crossOrigin is supported, output will be logged to console. Otherwise, it will throw an error.
HTMLVideoElement objects should have a crossOrigin property that corresponds to the crossorigin attribute on the element. If a video element has this attribute and the appropriate headers are delivered from the server, drawing the video to a canvas should not set the canvas to a “dirty” security state. It should still be possible to read back pixels from that canvas.
This should also work with WebGL, once video textures are implemented. Refer to this ticket:
Dev Channel specific:
Comments and activity
- Microsoft Edge Team
Changed Assigned To to “Venkat K.”
Changed Assigned To from “Venkat K.” to “IE F.”
Changed Status to “Fixed, not yet flighted”