You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that on the Vercel adapter docs page, settings.png isn't displayed in the "Node version" section. Chrome shows a warning in the console that this is due to Cross-Origin Resource Blocking. This page explains that when an <img>'s src has x-content-type-options set to nosniff and a (wrong) content-type: text/html header (which both applies to that image), CORB will block the response
"Vercel project settings" alt text is displayed instead of the actual image
Logs
Cross-Origin Read Blocking (CORB) blocked cross-origin response https://github.com/sveltejs/kit/blob/master/packages/adapter-vercel/settings.png with MIME type text/html. See https://www.chromestatus.com/feature/5629709824032768 for more details.
Can reproduce in Arc (Chromium), Firefox and Safari
The text was updated successfully, but these errors were encountered:
msonnberger
changed the title
[docs] External images won't load because of [CORB](https://chromium.googlesource.com/chromium/src/+/master/services/network/cross_origin_read_blocking_explainer.md))
[docs] External images won't load because of [CORB](https://chromium.googlesource.com/chromium/src/+/master/services/network/cross_origin_read_blocking_explainer.md)
Jan 19, 2023
msonnberger
changed the title
[docs] External images won't load because of [CORB](https://chromium.googlesource.com/chromium/src/+/master/services/network/cross_origin_read_blocking_explainer.md)
[docs] External images won't load because of CORBJan 19, 2023
Maybe colocate assets needed for docs to avoid this. Some links are also absolute (they had to be when it was in the adapters readme) that can now be relative.
Describe the bug
I noticed that on the Vercel adapter docs page,
settings.png
isn't displayed in the "Node version" section. Chrome shows a warning in the console that this is due toCross-Origin Resource Blocking
. This page explains that when an<img>
'ssrc
hasx-content-type-options
set tonosniff
and a (wrong)content-type: text/html
header (which both applies to that image), CORB will block the responseReproduction
Logs
System Info
Severity
annoyance
Additional Information
Can reproduce in Arc (Chromium), Firefox and Safari
The text was updated successfully, but these errors were encountered: