- From: Aaron Gustafson <aaron@easy-designs.net>
- Date: Mon, 1 Dec 2014 15:35:04 -0500
- To: public-web-perf@w3.org
- Message-ID: <CALWPYzGrrrOi--Wk=yFuu3wBBXawTbTQYMOj+PmppxfVA=fuig@mail.gmail.com>
Hello all, Please excuse me if this has been covered already. I could only find a single thread reference on the mailing list ( http://lists.w3.org/Archives/Public/public-web-perf/2013Apr/0060.html) and no response from the draft authors, so I’m bringing it up again. If there is another thread that discusses this, I would appreciate a link. In April of last year, Jake brought up the "defer" attribute for images (and other resources). In reading the Resource Hints draft, the concept of lazy loading or allowing the browser to determine the loading process, but to be aware of a low-priority resource seems to have been lost. It was part of the now-abandoned Resource Priorities draft (defer, lazyload). The Resource Hints draft seems to focus entirely on prioritizing assets and domains (which is understandable), but does not seem to offer an option for de-prioritizing assets. Are we to assume that deprioritization would be the default behavior if prioritization instructions are provided? In not, where are we at with respect to a declarative de-prioritization instruction? Cheers, Aaron ---- Aaron Gustafson Founder & Technical Lead Easy Designs, LLC @aarongustafson
Received on Monday, 1 December 2014 20:35:51 UTC