consoledebuggoogle-chromegoogle-chrome-extensions
Is there a way to prevent extensions from showing up in the console of the developer tools window? It's annoying to be looking for JavaScript errors and have to ignore errors that are always there. I know from this question you can use Incognito mode, but I don't want to have to develop in a separate browser window with all of the shortcomings of Incognito mode.
If there isn't a good answer to this, how do I run down the offending extension, short of turning them off one at a time?
You are forgetting the following:
The more popular an extension is, the smaller is the chance of nobody noticing that the add-on does something harmful.
In contrast to that, if you install some extension that nobody else has used before, you risk more than, let's say, installing AdBlock. Considering that so many people are using it, it is almost safe to say: Someone would have noticed unusual traffic.
In fact, all extensions disclose their source code, so anybody could basically go ahead and look for anything suspicious themselves.
The warnings are just there so you can't blame the browser vendors for any damage done, in case you install something that goes rogue with your data. Always read the reviews of add-ons that look suspect to you before installing them.
Also note that, for example Google can check the submissions:
While Google is not obligated to monitor the Products or their content, Google may at any time review or test your Products and their source code for compliance with this Agreement, the Google Chrome Web Store Program Policies, and any other applicable terms, obligations, laws, or regulations, and may use automated means to conduct such review
Removal of an extension can of course cause some trouble to the developer.
Chrome itself features user profiles and fast user switching. Add a user from chrome://settings/.
You can test your webapp from the new user you created.
Switching between users is just a matter of clicking on the icon on the top left and then select the other user
Best Answer
I realize this is an older question, but there is a better way than systematically disabling all your extensions to find out which one is throwing an error.
Hover the mouse pointer over the file name for the error in the console. You'll see a long string of gobbledygook. Part of that is an id that is unique for each extension. Take a moment and memorize the first few characters, in the image below they are pmejh:
Then go to your installed extensions at chrome://extensions and hover over each details link looking for a URL in the bottom left of the window that contains the characters you memorized.