This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24597 - Maybe make the <img> fetch outlive the document (like ping)
Summary: Maybe make the <img> fetch outlive the document (like ping)
Status: RESOLVED MOVED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other All
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-10 12:09 UTC by contributor
Modified: 2019-03-29 21:04 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2014-02-10 12:09:35 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/embedded-content-1.html
Multipage: http://www.whatwg.org/C#update-the-image-data
Complete: http://www.whatwg.org/c#update-the-image-data
Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/

Comment:
Maybe make the fetch outlive the document (like ping), see
http://www.w3.org/mid/73D56449-E4C2-4206-A5D0-136720F5747D@apple.com

Posted from: 90.230.218.37 by simonp@opera.com
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_5_8) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.90 Safari/537.1
Comment 1 Ian 'Hixie' Hickson 2014-02-10 21:12:32 UTC 
Is that reliably implemented by everyone?

If so, Fetch is going to need to provide an explicit "keep this alive even if it's no longer got a Document" mode, because <img> loads can't be unrelated to their Document, obviously.
Comment 2 Anne 2014-02-11 13:25:49 UTC 
Currently Fetch makes it the task of HTML to clean up after itself. E.g. during document unloading you could go through your list of outstanding fetches and terminate them all. You'll need to keep a list anyway for specifications such as http://www.w3c-test.org/webperf/specs/ResourceTiming/ although they probably have not thought about proper integration yet...
Comment 3 Ian 'Hixie' Hickson 2014-02-11 19:50:22 UTC 
I'm not aware of any issue relating to Resource Timing, can you file a bug if that needs integration on the HTML side?

Anyway, I guess I can just manually label each fetch task on my side.
Comment 4 Anne 2014-02-12 14:54:51 UTC 
I emailed http://lists.w3.org/Archives/Public/public-web-perf/2014Feb/0029.html to them. Hopefully they can take responsibility and file bugs. I suppose they might file against W3C HTML :/
Comment 5 Anne 2015-09-21 08:29:02 UTC 
I think this requires adding "keep-alive flag" to the request instances used for <img>. Seems fairly straightforward.
Comment 6 Simon Pieters 2015-09-21 09:06:28 UTC 
Need to investigate if this happens for all images or just those created at unload-time.
Comment 7 Domenic Denicola 2019-03-29 21:04:01 UTC 
https://github.com/whatwg/html/issues/1655