24080 fetch 2013-12-12 21:24:23 +0000 Integrate with Fetch specification 2015-09-16 11:54:46 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED MOVED blocked on dependencies P3 normal Unsorted 26836 24031 24137 24613 24659 26830 1 ian ian annevk bobbyholley bzbarsky ian mike mkwst contributor oldest_to_newest 97538 0 ian 2013-12-12 21:24:23 +0000 97592 1 annevk 2013-12-13 14:34:38 +0000 Please consider "HTML fetch" obsolete when you do this. Please first review and request appropriate hooks. The current setup is very barebones and requires setting up requests to pass to fetch and handling responses that are returned. I'm fine with adding sugar, but I have not yet figured out exactly what that should be myself. 100152 2 annevk 2014-02-10 14:56:08 +0000 So in bug 24137 comment 19 you say we need to pick the right event loop. This would be a "networking task source" associated with a set of browsing contexts or a worker. So should you pass in either a Document or a WorkerGlobalScope as a handle for Fetch to find the relevant things? 105367 3 ian 2014-05-07 23:07:13 +0000 Ideally I'd pass in an event loop, no? I'm not really sure. How confident are you in the current fetch spec text? What exactly is it I should be merging in? In bug 24613 you said something about one of the algorithms being something you want back into HTML? 105436 4 annevk 2014-05-08 14:28:41 +0000 The problem I have is that everyone uses Fetch, but nobody really cares about the details and overall platform coherence. So it's really hard to figure out what parameters Fetch needs and what the easiest setup could be given the various requirements we have. E.g. for service workers we need a global. We can use that global for CSP too. Can we use it for Referer determination (also partially a CSP matter these days)? We always need an origin, does that need to be passed in explicitly, or can we get that from a global too? Most of the structure is sound I think, but the details are not cemented. 105437 5 annevk 2014-05-08 14:30:14 +0000 Once HTML uses this, it should use the http://fetch.spec.whatwg.org/#concept-fetch algorithm almost directly, perhaps with shorthands defined for more complicated fetching scenarios, such as "image fetch". 109709 6 ian 2014-07-31 21:14:28 +0000 (Currently discussing Fetch's use of 'client' in webappsec.) 111218 7 ian 2014-09-08 23:34:18 +0000 Why do you need a global for service workers? 111240 8 annevk 2014-09-09 09:11:38 +0000 Currently we check if the client (environment / global object) is from a service worker to go directly to the network. (We also use that client for referrer, origin, etc.) 111275 9 ian 2014-09-09 15:57:34 +0000 Maybe we should extend the script settings object to just me an "environment settings object", and shunt that around. That would let us maintain specific referrers, origins, event loops, etc, things that aren't always set with a global or Realm. There's a global hung off the side of the settings object already. 111278 10 annevk 2014-09-09 16:06:10 +0000 An environment settings object would work for me. That would indeed help with queuing tasks on the right event loop as well. 123228 11 annevk 2015-09-16 11:54:46 +0000 https://github.com/whatwg/html/issues/95