[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] EME and its interaction with WebGL

A few clarifying questions:

Does "EME" stand for "embedded media element"?

Does the video element obey the same-origin policy, or use CORS headers? It sounds like you're describing the cross domain tainting business.

Also curious about the larger context of this question.


On Thu, Feb 28, 2013 at 9:56 AM, Florian Bösch <pyalot@gmail.com> wrote:
I was wondering about the implications of having an EME element (video) on the page and its interaction with WebGL.

The HTMLVideoElement can be used by calls to texture2D, and as I've shown dependent lookups and vertex shader lookups can be used to extract content (other than toDataURL and readPixels).

Is it a given that the presence of an EME video on a page also containing a gl context will disable:
- dependent lookups in fragment shaders?
- vertex shader texture lookups?
- toDataURL of canvases?
- readPixels?