Re: [whatwg/fetch] preload, destinations, and module scripts (#486)

@domenic do you see the combinatorial possibilities extending beyond these four? Or can we agree that a unified `module` goal may form a possible common denominator? I'm don't see how this is a strong argument for a new rel otherwise.

I'm advocating rel=preload simply because the naive user-facing conceptual models of the web should embrace outward simplicity and reusability as far as possible to remain understandable to all, but I'm more than happy to step back on that if there are untenable spec differences here.

Note also that I'm not trying to throw out the concept of a full graph preload entirely - simply to say that what is needed _urgently_ is a spec that will allow a low-level network-layer caching of module resources. A separate rel for a graph-based preload could potentially be addressed later on - perhaps then more generally too in a way that applies similarly for css, picking up a truly unique semantic meaning then in the process.

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