New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 337734 link

Starred by 65 users

Issue metadata

Status: WontFix
Last visit > 30 days ago
Closed: Jan 2014
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression

  • Only users with EditIssue permission may comment.

Sign in to add a comment

"Disable developer mode extensions" popup keeps appearing even though i am a developer

Reported by, Jan 24 2014

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.46 Safari/537.36

Steps to reproduce the problem:
1. Set up an extension in developer mode
2. Close and reopen the browser
3. Dismiss the developer-mode popup
4. Close and reopen the browser

What is the expected behavior?
The developer mode popup does not reappear, or reappears infrequently

What went wrong?
The developer mode popup reappears on every browser load.

Did this work before? Yes Prior to the introduction of the "Disable developer mode extensions" dialog (32 i think)

Chrome version: 33.0.1750.46  Channel: beta
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 12.0 r0

I'm a developer, i acknowledged this setting already and know that it is on, the popup should not reappear every time i open the browser.. It's very annoying to have to dismiss this popup on every load - especially since it seems to load asynchronously and steal focus from whatever i'm doing e.g. browsing through nested bookmark trees, causing position to be totally lost
Labels: -Cr-UI -Type-Bug Cr-Platform-Extensions-API Type-Bug-Regression M-34
Status: Assigned
Able to reproduce the issue (Attached screenshot) and below is the Cl:

Suspecting - r240596	

dvh@ Please let us know if this is an intended change ?
123 KB View Download
Status: WontFix
This is part of a defense in depth against force-installed extensions, and should only be present in windows stable/beta channels. Unfortunately there aren't great ways when reading the prefs at startup time to tell the difference between someone choosing to load an extension in development mode and malicious software on their machine having forcibly altered their prefs without their knowledge, so this dialog has to be shown at every startup. 
Is there really no way we can stop these? Can't you add a flag which we can tick to hide the message or add a ton of steps on the extension page to confirm that the extension in question is approved by the user?
Like the original poster, I have one extension which I've built, but don't want to run Chrome in Dev/Canary as I need it to be stable for day to day work.
Sorry, we know it is annoying, but you the malware writers have already shown that they are willing to modify command line flags and directly modify preferences files, so we don't see any way we could do that and have this warning still remain effective. 

One option you might consider is uploading your extension to the webstore, but instead of making it public, you can leave it hidden and publish only to people who have the link (or a set of trusted tester accounts). 

 Issue 339159  has been merged into this issue.

Comment 6 by, Feb 13 2014

This also happens with Roboform, which is in the Chrome webstore. 

Comment 7 by Deleted ...@, Feb 21 2014

All the hoops you have to jump through to put extensions on the webstore for personal use just to get rid of this message are ridiculous.

A lot of the extensions I've made are for websites that I don't own, for companies that aren't going to authorise association.

Just give the user a way to disable the warning and tell them that they do so at their own risk.

Comment 8 by, Feb 21 2014

Wow. This is retarded.
It's basically Google saying F.U. to developers. You don't want us as Chrome users anymore?

Is it so hard to have an option on that dialog that says "Keep Enabled" and when you click it, you get a series of "Are you really sure" messages that warns you of the dangers. The final Are you Sure prompt could tell you how to stop it, which could be something like having to add a command parameter to your Chrome shortcut.

Now I gotta go see if I can find an installer for Chrome 31 (the last without this message I think) and then I'll have to add a hosts file entry to whatever the google updater domain is to stop it auto-updating. Real secure.
Found the solution I need after finding version 32 on another machine.

1. Disabled chrome updates (services.msc, msconfig.exe, Hosts file for Before proceeding, make sure in "Chrome -> About" that it fails to figure out if it's up to date and that the updater services are disabled.
2. In program files folder, rename the 33 folder to something else and rename chrome.exe to something else. Then copy over the program files 32 folder and the chrome.exe from your provider machine into 'this' machine.
3. In your Chrome AppData folder, rename "Default" folder (as "Default33", or something) and start Chrome. It will make a new Default folder. Close Chrome.
4. Copy stuff from the Default33 into Default. All the bookmarks, cookies, local storage, extensions etc.
Start Chrome, you might have to re-login to your google account (once only).
I did this and have all my bookmarks, I even have all my bookmarks bar bookmarks in the same places, and all my extensions (yes the developer ones, f u google) there and working.

Version 32 all the way for me from now on.

I hope Chrome ends up having multiple versions out there, like IE does, if the developers want to introduce features like this. They deserve what they get, just like the MSFT developers who made the decision to not allow new IE versions to be installed on onlder versions of Windows. As they say in Germany, "Selbe Schuld!".

Comment 11 by, Feb 21 2014

Firefox, here I come

Comment 12 by Deleted ...@, Feb 21 2014

1) I did not hack or create malware in any way.
2) I have had chrome and roboform for over a year and this is a new problem.
3) I used chrome's tools to add roboform as an extenstion.
4) I have not recently updated roboform.
5) If chrome has been updated it was an automatic update transparent to me as the user.
Conclusion, chrome needs to address this problem.
184 KB View Download
>Conclusion, chrome needs to address this problem

My conclusion is that the Chrome developers are going the same way the IE developers did. Because they're number 1 they think they can dictate how things will be. Shame there isn't a historical precedent of how that can fail, oh wait, there is.

Labels: Restrict-AddIssueComment-EditIssue
FYI, this dialog is only present in the stable and beta channels on Windows. Our suggestion is that developers consider switching to the dev channel of chrome. 

The bug tracker isn't designed to be a discussion forum, so I'm closing comments on this issue. But feel free to continue the discussion on one of our mailing lists that are intended for this: (for extensions developers) (for apps developers) (for general user discussion)

 Issue 346049  has been merged into this issue.
 Issue 347146  has been merged into this issue.
 Issue 347146  has been merged into this issue.
 Issue 347146  has been merged into this issue.
 Issue 347146  has been merged into this issue.
 Issue 347146  has been merged into this issue.
 Issue 347146  has been merged into this issue.
 Issue 349143  has been merged into this issue.

Comment 23 by, Apr 14 2014

To those who don't want to be bothered by the "Disable developer mode extensions" dialog: Just switch to the Beta channel:
1. Visit
2. Click on "Download Chrome Beta" and install.

It is similar to Chrome stable, except that its set of features is about six week ahead of the stable channel.
In addition, some extension features in development are also available on this channel. If you're using unpacked extensions, then odds are that you are a power user, so this richer set of extension APIs will probably bring you more joy.

The "email addresses" in comment 14 are mailing lists. They can be viewed publicly at: (for extensions developers) (for apps developers) (for general user discussion)

Comment 24 by, Apr 14 2014

Oops, disregard my previous comment. The popup also shows up on the Beta channel. You have to install Chrome from the dev channel:

(or use Linux, Mac or Chrome OS)

Comment 25 by, May 14 2015

Note: Switching to the Dev channel does not work any more. The only ways to load extensions without the popup is via policies.


Sign in to add a comment