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

[whatwg] Unnecessary loading of fallback content in canvas element

From: Charles Pritchard <chuck@jumis.com>
Date: Sat, 8 Jan 2011 14:45:17 -0800
Message-ID: <8A0BDA6B-FF8F-4623-9F37-867C6E1F1DCC@jumis.com>

Date: Sat, 08 Jan 2011 17:41:33 +0100
From: Benjamin Poulain <benjamin.poulain@nokia.com>
Subject: Re: [whatwg] Unnecessary loading of fallback content in
   canvas    element

On 01/08/2011 12:57 AM, ext Charles Pritchard wrote:
> Let me know if this has been discussed before:
> 
> Loading an html page containing:
> <canvas><img src="fallback.jpg" /></canvas>
> loads the fallback.jpg image, even when canvas is supported.
> 
> Is this intentional, or simply the easiest route for the moment?

I would say that is the indented behavior.

....

For example:
"When a canvas element represents embedded content, the user can still 
focus descendants of the canvas element (in the fallback content)."

Since the content is available, I think it is normal for it to follow 
the normal behavior.

cheers,
Benjamin


Benjamin,

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.
Received on Saturday, 8 January 2011 14:45:17 UTC

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