On Wed, Jan 8, 2014 at 7:32 PM, Ilya Grigorik <igrigorik@google.com> wrote: > As per our discussions before the break, I've added a "use cases" section > to the document to highlight where and how each hint can be used: > https://docs.google.com/a/google.com/document/d/1HeTVglnZHD_mGSaID1gUZPqLAa1lXWObV-Zkx6q_HF4/edit#heading=h.nbuj0xq5vk0g > > Any additional examples + general feedback on what's there would be much > appreciated! > Looks awesome! I have my reservations regarding using "preload" and "preload lazyload" to signify semantically different types of resources. While "prefetch" was confusing, it had this advantage, since these types of resources should behave differently under certain scenarios. maybe "preload" and "nextpage-preload"? A few specific comments: * In the "preload - current page" section - What's the reason for "UA should not apply any content-specific processing on preloaded resources"? I agree that it's probably not a good idea to do so when the CPU is busy, but assuming it is not, why shouldn't the UA process these resources (e.g. JS parsing or image decoding). OTOH, it *must* not execute JS or apply CSS them before they appear in the page. * In the "preload+lazyload" section - Shouldn't the "UA should not cancel preload requests across page navigations" part refer *only* the preload+lazyload? I'd assume that requests for resources that are supposed to be preloaded for current page would be canceled across navigations. * "Prefetch hints should be interoperable with Link headers to allow simple FEO / proxy optimization" - That would indeed be extremely helpful for FEO proxies * In the use-cases section, shouldn't the "prefetch" section be renamed to "preload+lazyload"?
Received on Monday, 13 January 2014 12:17:47 UTC