W3C home > Mailing lists > Public > whatwg@whatwg.org > January 2011

[whatwg] Unnecessary loading of fallback content in canvas element

From: Benjamin Poulain <benjamin.poulain@nokia.com>
Date: Sun, 09 Jan 2011 00:02:47 +0100
Message-ID: <4D28ED17.9030800@nokia.com>
On 01/08/2011 11:45 PM, ext Charles Pritchard wrote:
> My point was that the resources are requested, instead of aborted.
> Yes, the elements should be in the DOM and focusable (and I've opened
> a webkit bug for that) -- my point is that an img tag should not
> spawn a network request during page load, for the fallback content
> unnecessarily.
>
> After page load, it makes sense for img and iframe; as injected by
> scripting; prior to that, it seems wasteful, it seems that
> img.abort() should be called.

My point is that such behavior would create differences in behavior 
depending on where the image is in the dom.

Once the page is loaded, one would expect all images to be available. 
Which would not be the case if images are not loaded, the one under 
canvas would have a different behavior.

I understand your point, loading stuff is not a free operation. I just 
think not doing it would make things even more complicated for content 
provider.

cheers,
Benjamin
Received on Saturday, 8 January 2011 15:02:47 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:29 UTC