We've thought about this.  Right now, the closest solution is to enable the flag chrome://flags/#extension-active-script-permission, which makes extensions requiring all urls require user consent (and gives options for "always run on this site", etc).  Note that it's still experimental and in development, and has some very rough UI edges.  But it should serve the purpose of giving you more control over when extensions act.

It's possible that we'll also provide a blacklisting functionality to disallow all extensions from acting on certain sites as part of the same project (I think the canonical bug is issue 362353).  If we don't, it's unlikely we'll get to this separately any time in the future.  Marking as available in case someone else is ambitious enough to take this on separately.

please

 Issue 766147  has been merged into this issue.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Devlin: I think this is sort of fixed with runtime host permissions. Assigning this to you, so you can triage this appropriately.