Assign to myself to kick start the investigation and discussion.

+kbr as FYI since we should figure out how to let WebGL work with these protected textures for VR or other custom rendering solutions on protected content.

Adding WebGL as a component. We could plausibly allocate the internal WebGL back buffer (which isn't user-accessible) as protected, to allow developers to sample these protected textures, but only write the results to the back buffer and not to user-defined textures.

liberato: Is "secure texture" still on your radar? Does it fit in your picture of the AndroidOverlay world?

yes, still on my radar, and could probably be added to AndroidVideoSurfaceChooser fairly easily.

however, i think that there are open questions about how to integrate secure textures with compositor (e.g., can we just get a secure context for the browser compositor, or do we need to be more careful than that to avoid the driver getting mad at our shaders?)

liberato: Is this something we still want to do?

in principle, yes.  however, as far as i know, the compositor doesn't understand these things yet.  there's a significant amount of work there.

amount of media work isn't too bad once the compositor knows how to handle a secure textuer.