On Mon, Mar 20, 2023 at 11:47 AM Yoav Weiss <[email protected]> wrote:
> Thanks for sending the intent and for experimenting with the MemoryCache! > > On Fri, Mar 17, 2023 at 7:08 PM 'Jiacheng Guo' via blink-dev < > [email protected]> wrote: > >> Contact [email protected] >> >> Explainer >> https://docs.google.com/document/d/1jcdXkoFBbdxmp_EYIrrOJvEgYd0hGBAr4Nbno7KWnIs/edit?usp=sharing >> >> SpecificationThe feature is not web-spec related. >> > > The situation as I remember it is a bit more complex than that :) > I think the memory cache is defined for images > <https://html.spec.whatwg.org/multipage/#the-list-of-available-images>, > but not for other resource types. > So if we end up changing the behavior for images, it'd be good to see if > we can reflect that behavior change in the spec. > And ideally, it'd be great if we're able to actually specify the behavior > of the memory cache once we figure out where we want it to land, as I > believe it is observable. (Through ResourceTiming, as well as timing in > general). > See spec meta-bug for context: https://github.com/whatwg/html/issues/6110 There are lots of existing interop issues around memory cache, we should try to make things better there (or at least not make them worse...) interoperability-wise. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJn%3DMYarzcCbJK5e5WYeeEM-QcMqF8-BbvbX%2BQ800zr-H8g2Bw%40mail.gmail.com.
