One more question - this applies to both <link rel=prefetch> and speculation rules, right? Developers would need to set (at least) short lifetime cache-control headers for both?
On Thursday, November 28, 2024 at 11:26:51 AM UTC+1 Yoav Weiss wrote: > Also, seems worthwhile for +Barry Pollard <barrypoll...@google.com> or > someone else to make some noise on that front.. > > On Thu, Nov 28, 2024 at 11:22 AM Yoav Weiss (@Shopify) < > yoavwe...@chromium.org> wrote: > >> >> >> On Thu, Nov 28, 2024 at 11:19 AM Noam Rosenthal <nrosent...@chromium.org> >> wrote: >> >>> On Thu, Nov 28, 2024 at 10:11 AM Yoav Weiss (@Shopify) >>> <yoavwe...@chromium.org> wrote: >>> > >>> > Refreshing my memory, as it's been a while - shipping this means that >>> web developers would need to set their HTML's caching headers to be >>> cacheable (even with a short lifetime) to ensure that prefetches are >>> actually useful? >>> >>> Correct. >>> >>> > >>> > Should we add some console logs (and maybe web-exposed reports) on >>> prefetches that are not cacheable? (as a followup) >>> >>> I wouldn't use console logs for this kind of thing, that's a very >>> crowded piece of real estate. But some sort of performance-panel >>> insights perhaps? >>> >> >> Sure, I meant "console logs" as a generic term for "surfacing this info >> to developers in the lab". I have no strong opinions regarding the specific >> surface. >> >> -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6edfe1c8-3565-4f08-8ebd-30ae67a38efdn%40chromium.org.
