-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
The "list of available images" and origin #5674
Comments
This seems reasonable. Any objections? |
Is this a general property of "memory cache" keys? It makes sense to me it cannot span origins. It should not be able to span top-level sites either, but that's probably best tackled separately. cc @emilio |
Chrome's memory cache is effectively keyed by requestor origin as well, so I think this is general property for us at least. |
Sure, but I don't get why the key needs to be in the document's "list of available images". Why is that desirable? For a given document, the origin is always the same, right? (maybe modulo |
I believe the spec allows for a document’s list of available images to be shared with any other document at any time |
Yeah, it seems like then we should key off the origin then. |
Hi,
Currently https://html.spec.whatwg.org/multipage/images.html#the-list-of-available-images says:
I think we should always attach the origin to the matching key, because that information is pretty important even for No CORS images - CORS-sameoriginness is one example.
cc: @domfarolino
The text was updated successfully, but these errors were encountered: