You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The img element displays resources of the "image" kind. Traditionally such resources have been opaque and considered replaced content. However, with the introduction of formats such as SVG the images can now sometimes have a DOM of their own.
The img element should provide access to the DOM of the subresource in the same style as the iframe element already does.
The text was updated successfully, but these errors were encountered:
The way to think about this isn't that images always go in img, and some images have DOM. It's that, if you want an opaque image, you use img. If you want a sub-document such as an SVG image, you use iframe.
So I don't think we'll make any change to the spec here; iframe already covers the use case you want.
We could consider adding a note to the spec, if that would help folks like yourself understand better that iframe is for sub-documents, and img is for rasterized images?
If only the img element was the only option other than iframe to display images. But as I hear, it's not. And that's not counting css. This can be seen in #4474.
The img element displays resources of the "image" kind. Traditionally such resources have been opaque and considered replaced content. However, with the introduction of formats such as SVG the images can now sometimes have a DOM of their own.
The img element should provide access to the DOM of the subresource in the same style as the iframe element already does.
The text was updated successfully, but these errors were encountered: