Re: [w3ctag/design-reviews] <link> rel="modulepreload" (#213)

Hey all,

Took this up at this week's F2F in London.

Thanks for filing a design review. We've looked through the design doc and now (relatively old) issues around the design and understand that the design space is highly contended. It looks like all permutations of `preload`, `prefetch`, `as` and `type` were considered, so there isn't much to discuss. A few points jump out, though:

 * The strongest argument for `<link rel="modulepreload">` (vs. regular `"preload"`) is that Modules are expected to be deep graphs, and so lazy fetching behavior needs to be admitted. From traces we've seen, this seems just as true for stylesheets. The lack of symmetry is problematic. We'd like to see an analogue for CSS added that will enable the UA to eagerly and recursively fetch and perhaps pre-process `@import`'d stylesheets and referenced fonts/images/etc.
 * as noted in some of the source discussion, it's unsatisfying from a layering perspective that there's no way to emulate this behavior from `fetch()`. Is there still active work on a destination hint?

Overall this looks good and the design seems to be a good compromise in a difficult space. Best of luck with your implementation.

/cc @domenic @annevk @plinss 

-- 
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-362641513