[Bug - Edge Addons] Edge Incorrectly Disables Extensions with Non-Default Search Provider and Displays Misleading Warning when search_provider.is_default == false

[AwesomeExtensions]

In Microsoft Edge, extensions that declare a chrome_settings_overrides search provider in their manifest.json with "is_default": false are unexpectedly disabled upon installation or update.

Edge presents a misleading warning to users stating:

"This extension tried to change your default search engine setting."

This message is inaccurate because setting "is_default": false explicitly avoids modifying the user's default search engine.

As a result:

• The extension is disabled without user confirmation.
• Users receive false information about an action that does not occur.

This behavior misleads users and disrupts extension functionality unnecessarily.

When does it happen

If extension have manifest.json with: chrome_settings_overrides search provider defined with "is_default" value set to false

• The extension is disabled without user confirmation:

(notice: "Installed but disabled")

• Users receive false information about an action that does not occur

"This extension tried to change you default search engine setting"

This message is inaccurate and false as chrome_settings_overrides.search_provider.is_default is set to FALSE. If "false" is set the default enginge IS NOT CHANGED in the browser and this is information is misleading users of something that is not happening.

It happens when:

• user is manually installing extension from Edge Add-ons
• user is manually installing extension from Chrome Web Store
• already installed and turned on extension auto-updates with new version

Example in manifest.json (from my Extension)

"chrome_settings_overrides":
 {
   "search_provider":
   {
     "is_default": false,
     "keyword": "grokipedia",
     "name": "Awesome Grok & Grokipedia",
     "encoding": "UTF-8",
     "search_url": "https://grokipedia.pl/search.php?q={searchTerms}",
     "favicon_url": "https://grokipedia.pl/favicon.png"
   }
 }

To Reproduce Reproduction Steps This issue occurs in the following scenarios:

• Manual installation from the Edge Add-ons store.
• Manual installation from the Chrome Web Store.
• Auto-update of an already-installed and enabled extension to a new version.

Minimal Reproduction:

1. Create or download an extension with the following manifest.json configuration:

2. Install the extension in Edge via any of the methods above.
3. Observe the extension being disabled and the warning dialog appearing.

Expected Behavior

The extension should remain enabled after installation or update, as it does not alter the default search engine. No warning should be displayed, since no change to the default search engine is attempted.

Actual Behavior

The extension is automatically disabled. A misleading warning is shown, implying an unauthorized change to the default search engine.

Environment

Browser: Microsoft Edge (all versions tested; issue not observed in other Chromium-based browsers like Chrome or Brave).

OS: Windows 10 and 11 (tested).

Extension Type: Manifest V3

Additional Notes

This issue only affects Edge and appears to stem from overly aggressive enforcement of search provider policies, even when explicitly non-default. A more nuanced check for "is_default": true would resolve the false positives.

If needed, I can provide a minimal extension ZIP for testing.

Screenshots https://github.com/user-attachments/assets/325a5637-051b-4feb-a786-6c4192fb4412

[Rahul-Bauri]

Hi @AwesomeExtensions

Thank you for sharing the details about this bug. I’ll pass this information to our internal team for investigation and will update you here as soon as I receive any updates from them.

[AwesomeExtensions]

@Rahul-Bauri any progress with that issue? It's a high priority blocker

[Rahul-Bauri]

Hi @AwesomeExtensions we are currently investigating the issue and will follow up with the engineering team to resolve it as quickly as possible. In the meantime, please do share a sample ZIP file of the extension so the team can reproduce the same issue.

[AwesomeExtensions]

What is the progress with that issue?

[Rahul-Bauri]

Hi @AwesomeExtensions, got an update from the internal team that we are not considering "is_default": false and just considering if the extension has the capability to change default search engine, we have taken your feedback and will discuss internally about changing it, but for now its intentional and by design to show the warning

[AwesomeExtensions]

When this issue will be fixed?