What type of issue is this?

Incorrect support data (example: BrowserX says "86" but support was added in "40")

What information was incorrect, unhelpful, or incomplete?

chrome_settings_overrides on Chrome is only available for Windows and Mac: https://developer.chrome.com/docs/extensions/reference/manifest/chrome-settings-override

What browsers does this problem apply to, if applicable?

Chromium (Chrome, Edge 79+, Opera, Samsung Internet)

What did you expect to see?

An implementation note stating it's only supported on some browser builds like shown with search_provider.is_default with Firefox.

Maybe also mentions of behaviors observed in "more you want to share"

Did you test this? If so, how?

Encountered it while trying to add custom search engines via an extension on a Chromium 137.0.7151.68 Linux build.

On another device running Windows this same extension*¹ does what it should do.

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

• https://developer.chrome.com/docs/extensions/reference/manifest/chrome-settings-override
• https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/chrome_settings_overrides
• Chromium bugtracker 40717644#7 → marked as won't fix due to this API not being planned to be added to Linux or ChromeOS

Do you have anything more you want to share?

It seems like the following fields within chrome_settings_overrides are required for Chrome if search_provider is used;

• search_provider.favicon_url
  • Should be a HTTP or HTTPS url it seems, even in manifest V3. Making the manifest configuration incompatible between Chromium and Firefox.
• search_provider.is_default
• search_provider.encoding
  • Only if prepopulated_id isn't added.

MDN URL

https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/chrome_settings_overrides

MDN metadata