- From: L. David Baron <notifications@github.com>
- Date: Tue, 27 Nov 2018 22:29:59 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 28 November 2018 06:30:21 UTC
@domenic [wrote](https://github.com/w3ctag/design-reviews/issues/213#issuecomment-379430095) above: > It depends. Fetching subresources is an optional part of modulepreload, and not the most important part. Populating the module map is the primary goal. It's not clear to us (discussing in today's TAG call) from the explainer why that's the primary goal, given that the explainer starts off by talking about high-priority loading of subresources. I think it would help us to understand what the use case for that goal is -- maybe the explainer needs updates to explain that, or a different explainer needs to be written? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/213#issuecomment-442335197
Received on Wednesday, 28 November 2018 06:30:21 UTC