Re: [whatwg] Preloading and deferred loading of scripts and other resources

2014-09-08 Thread Ian Hickson
I got some feedback on my last e-mail to the effect that having the proposal sandwiched between the rationale and the examples of how it would be used made it hard to find, so I'm reproducing the proposal here (slightly updated based on feedback): --

Re: [whatwg] Preloading and deferred loading of scripts and other resources

2014-09-08 Thread Ilya Grigorik
On Mon, Sep 8, 2014 at 1:33 PM, Ian Hickson wrote: > > I really like your proposal for "as="... Concretely it could look > something > > like this: > > > > > href="/some/asset.css" > > as="stylesheet"(used to initialize default priority, headers, > > etc) > > load-set

Re: [whatwg] Preloading and deferred loading of scripts and other resources

2014-09-08 Thread Ian Hickson
On Mon, 8 Sep 2014, Ilya Grigorik wrote: > > Better or worse is not the point. I think the current proposal fails to > address the larger underlying problem. If it did, then that would be "worse". > The platform is missing a lower-level primitive (declarative and > imperative) that is able to

Re: [whatwg] Preloading and deferred loading of scripts and other resources

2014-09-08 Thread Ilya Grigorik
On Mon, Sep 8, 2014 at 7:59 PM, Ian Hickson wrote: > > The platform is missing a lower-level primitive (declarative and > > imperative) that is able to explain resource loading with the same > > expressive power as requests initiated by the browser itself. > > That isn't a problem. > I don't fol