Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define the "memory cache" #1400

Open
annevk opened this issue Feb 11, 2022 · 4 comments
Open

Define the "memory cache" #1400

annevk opened this issue Feb 11, 2022 · 4 comments
Labels
interop Implementations are not interoperable with each other

Comments

@annevk
Copy link
Member

annevk commented Feb 11, 2022

Aside from the preload cache, browsers have another cache for certain resources. The semantics differ across browsers and can impact whether service workers end up seeing a request, for instance. Ideally this would be better defined.

#590 tracked some of this discussion previously.

@annevk annevk added the interop Implementations are not interoperable with each other label Feb 11, 2022
@annevk annevk mentioned this issue Feb 11, 2022
2 tasks
@noamr
Copy link
Contributor

noamr commented Feb 11, 2022

Note: the memory cache is defined for images, here. However, it is implemented for other resources types as well (styles/fonts/...)

@noamr
Copy link
Contributor

noamr commented Feb 11, 2022

Some existing preloaded-related bugs that arose from lack of defined memory cache:
https://bugzilla.mozilla.org/show_bug.cgi?id=1743764
https://bugs.webkit.org/show_bug.cgi?id=233854

@domenic
Copy link
Member

domenic commented Feb 11, 2022

whatwg/html#6110 is the HTML-side issue for this.

@youennf
Copy link
Collaborator

youennf commented Jun 5, 2022

Service worker and memory cache relationship is also something that would be good to describe.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
interop Implementations are not interoperable with each other
Development

No branches or pull requests

4 participants