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

Re: [Public WebGL] Should texImage2D and texSubImage2D accept more element types?

On 5/31/12 1:07 AM, Glenn Maynard wrote:
I honestly don't really know what people use <object> for these days,
but given that it's something to do with plugins

Fwiw, <object data="image.png"> doesn't involve any plug-ins. It's just rendered the same way <img src="image.png"> is rendered.

it sounds like it's hard to define whether the contents are sensitive (like cross-origin
images) or not.

For the case when the <object> is loading an image, you'd just define it the same way you do for <img>.

And the UA already has to have a concept of "<object> is loading an image". Load http://www.whatwg.org/specs/web-apps/current-work/multipage/the-iframe-element.html#object-type-detection and then scroll down to the next step (which is not directly linkable, sadly). The one that starts:

  8.  Handler: Handle the content as given by the first of the
      following cases that matches:

So speccing this case would actually be reasonably easy. "If the <object> element represents an image, do what you would do for <img>" (probably with a bit more detail, but not much, if you factor out the "do what you would do for <img>" bits of the spec).

I do agree it's not worth worrying about <object> too much; I included it as part of my description of current UA behavior.


You are currently subscribed to public_webgl@khronos.org.
To unsubscribe, send an email to majordomo@khronos.org with
the following command in the body of your email:
unsubscribe public_webgl