-
Notifications
You must be signed in to change notification settings - Fork 159
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
fetched icons fail in chrome when same-origin policy is present #1065
Labels
Comments
I think the spec is correct here and I think Chrome might be working as expected. However, someone might need to check one the Chrome side. |
I don't think I fully understand what is going on here, sorry. Do you have a demo page that we could look at? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I read #535, but that is only about the manifest itself.
With a same-origin CORP chrome devtools complains 'icon n failed to load'.
Their logger says:
even though a
crossorigin
attribute on thelink
to the manifest is given.It should say
sec-fetch-site: same-origin
. If I turn off same-origin altogether, it works as expected.Is this a bug in chrome, or am I missing something from the spec?
Firefox does not have this issue, their devtools show the images just fine. On Android a Chrome based fork I tried with also allows 'adding to homescreen' and shows an image. It's unclear whether that's just an upscaled favicon, though.
Cheers
The text was updated successfully, but these errors were encountered: