Hey Jiacheng!

What are other browsers doing on that front?

While I agree that this is not strictly web exposed (and hence doesn't
really fit the "intent to ship" mould), this is something developers need
to be aware of.

On Thu, Sep 22, 2022 at 5:43 PM Jiacheng Guo <[email protected]> wrote:

> *Contact emails*
> [email protected]
>
> *Specification*
> https://html.spec.whatwg.org/#processing-link-headers
>
> *Summary*
> Enforce the CORS policy specified in <link rel="icon"> labels.
>
> Currently chrome always use no-cors mode when fetching favicons even if
> cross-origin attribute is specified. The browser shall follow the
> cross-origin attribute.
>
> *Blink component*
>
> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ELoader%3EWebPackaging>
> Blink>SecurityFeature>CORS
>
> *Debuggability*
> If a favicon fetch fails with a CORS error, it will be reported on the
> developer tools.
>

Can you also report such failures as Deprecation Reports
<https://wicg.github.io/deprecation-reporting/>?


>
> *Link to entry on the Chrome Platform Status*
> <https://chromestatus.com/feature/5047867052392448>
> https://chromestatus.com/feature/5199599585722368
>
> --
> 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/d0e9454f-62c1-4c43-a1e1-2b39743062bbn%40chromium.org
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/d0e9454f-62c1-4c43-a1e1-2b39743062bbn%40chromium.org?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CAL5BFfVvnfcOjvnJeGzxq%3DxHT9z89L4woSDG0_Ndt%2Bu582uB1w%40mail.gmail.com.

Reply via email to