favicon issues

[TimidRobot]

Issue Description

1. /favicon.ico redirects to https://creativecommons.org/wp-includes/images/w-logo-blue-white-bg.png
   • Theme must set CC site image. We mustn't serve a WordPress favicon
   • Server must return a 200 for /favicon.ico not a 302
2. https://creativecommons.org/wp-content/themes/vocabulary-theme/vocabulary/favicon/favicon.ico
   • Mozilla Firefox 145.0.2 gives a text error:

     The image https://creativecommons.org/wp-content/themes/vocabulary-theme/vocabulary/favicon/favicon.ico" cannot be displayed because it contains errors.

   • Safari Version 26.1 (21622.2.11.11.9) on macOS displays only a small question mark:
     • 
3. https://creativecommons.org/wp-content/themes/vocabulary-theme/vocabulary/favicon/favicon.svg doesn't render in when viewed directly
   • Maybe this is an idiosyncrasy of SVG?

Expectation

Favicons should work across clients. Even when clients fall outside our supported versions, we should not return bad data (WordPress favicon).

Environment

• Device: MacBook M1 Pro
• OS: macOS Tahoe 26.1

Additional context

• Replace favicon on CreativeCommons.org #32
• Update/reorganize assets and add favicons search#196
  • https://raw.githubusercontent.com/creativecommons/search/16461e5a4d559cbd3b63c22f2182bd2c09d96943/docs/favicon.ico
• Favicon and app icons not present on website index-prototype#6
• How to set WordPress Favicon | Site Icons | WordPress.com Support
• do_favicon() – Function | Developer.WordPress.org

Resolution

• I would be interested in resolving this bug.

[possumbilities]

I don't get precisely the behavior described above.

If I test this in FF, even a more current version like 151.0.3, it downloads the .svg and not the .ico and there is no error. Even a direct link to the .svg works fine.

In Chrome it works fine (tested on another device).

But in older and current versions of Safari it downloads the .ico and the .svg attempts to load the .ico and then displays no favicon in the cases I've tested.

I don't in any of the above cases get the WordPress logo (unless I'm logged in). It showing up outside of being logged in sounds like a caching issue (either locally, or on the part of Cloudflare). Also favicon.ico has its issues within WP because WordPress has a core setting to set the favicon to an uploaded .png or load a default .png from core and has a bit of a redirect in place around the root favicon.ico file that does and does not get overridden depending on a lot of factors.

I have a suspicion that the type attribute is set incorrectly on the .ico, but I think the best course of action here is to stop supporting .ico entirely fully adopt .svg with a possible .png fallback. That should clear up most of the above. As for the remainder I'll keep researching.