[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Public WebGL] Should texImage2D and texSubImage2D accept more element types?
On Wed, May 30, 2012 at 12:35 PM, Boris Zbarsky <email@example.com>
In addition to those four, I believe Gecko will also accept the following right now:
HTMLInputElement (when it's an <input type="image">)
HTMLObjectElement (when rendering an image)
I'm not sure whether there are use cases for these, offhand.
FWIW, HTMLInputElement doesn't seem worth spending time on. Even if there are use cases for it, you can always just set up an <img> with the same @src, which I'd expect would be fed from the same network request or cache entry. Supporting it directly doesn't seem worth much--nobody's trying to align <input> and <img>, after all.
I honestly don't really know what people use <object> for these days, but given that it's something to do with plugins, it sounds like it's hard to define whether the contents are sensitive (like cross-origin images) or not. I suppose if it's supported here, the security details can be left as an implementation detail (since the plugins themselves are implementation details anyway).