- From: Guy Bedford <notifications@github.com>
- Date: Thu, 24 Aug 2017 18:32:50 +0000 (UTC)
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 24 August 2017 18:33:17 UTC
@domenic the argument there seems to jump to some conclusions already. > @rniwa the above discussion goes into some fairly extensive detail on why rel=preload as=modulescript can't work, but I guess it was not summarized nicely for newcomers. Let me try. Here are the main reasons why rel=preload as=modulescript doesn't work. > We need to populate the module map, not the preload cache/HTTP cache. In particular, this means that the preload processing model, which e.g. re-fetches whenever various attributes change, does not make sense, since the module map is immutable. I don't see it as obvious that this is a necessity. Can a preload cache not be used by the module loading algorithm to populate the module map? > We need to fetch all the dependent modules, not just the single resource pointed to by the link tag; the processing model for rel=preload does not allow this. As discussed, above a simple solution may be to simply skip this. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/486#issuecomment-324719311
Received on Thursday, 24 August 2017 18:33:17 UTC