MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]: No way to toggle extensions developer mode

Open
#5,088 2 comments 1 reaction 1 assignee View on GitHub

@chetanpandey1266 is already working on this.

Since Feb 5, 2025.

feature request
Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

What happened?

Hello,

The problem im facing is i require some Browser Extensions for my App but many Browser Extensions need extensions developer mode enabled. (extensions.ui.developer_mode).
But after researching for a while i could not find any way to toggle this using webview2 on my win32 c++ app.

For example that option can be set in selenium using prefs. See this stackoverflow issue.

The only current way i found to enable it is by creating a new Profile in edge Browser and then enabling extensions developer mode there in the "chrome://extensions" ui. After that i could copy that profile over to my webview2 user data folder replacing the "Default" profile. This allowed me to have the option enabled.

Also directly editing the "Secure Preferences" file in the "Default" webview2 profile is not possible as well as this file is protected. Profiles with extensions developer mode enabled have it set here to True under extensions.ui.developer_mode.

Would appreciate any help or if this is not yet possible for it to be added.

Importance

Important. My app's user experience is significantly compromised.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

132.0.2957.127

SDK Version

1.0.2277.86

Framework

Win32

Operating System

Windows 11

OS Version

10.0.22631

Repro steps

Try enabling extensions.ui.developer_mode

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

No, this never worked

Last working version (if regression)

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.