You can try running chrome with --extensions-on-chrome-urls --whitelisted-extension-id=ihlenndgcmojhcghmfjfneahoeklbjjh command line.

As for general permission, this feature was requested multiple times but it won't happen, at least in the near future. It'd super-easy for a malware extension to modify the secure internal pages and deceive users, steal user data, install all kind of stuff, access super-powerful private chrome API available on chrome:// pages internally. To counter that, each update of an extension that wants to run on chrome:// pages would need to be reviewed by a very qualified developer to get whitelisted like it's done on mozilla addons site, and it's a huge challenge with the result that benefits only a relatively infinitesimal amount of power users while Chromium/Chrome is primarily for everyone. And even if it were possible, current whitelisting mechanism is not practical because it's embedded in the C++ source code of chromium hence maintained only for Google's own extensions like ChromeVox that runs on chrome:// pages.

Hmm, the above-mentioned command line might not be sufficient. You might need to make a copy of cVim extension directory, edit manifest.json, and add "chrome://*" to the "content_scripts" block in "matches" comma-separated list. And maybe "about:blank", but I'm not sure it'll work. Then you'll have to install this modified extension on chrome://extensions page instead of the one from webstore.

>--extensions-on-chrome-urls

Unsupported.

--whitelisted-extension-id=ihlenndgcmojhcghmfjfneahoeklbjjh

No effect at about:blank.

>super-easy for a malware

Guess users who suffers from maleware and users who use cVim-like extebsions are different users. It would be nice to see a checkbox or a flag "switch off all stupid security and let me just use the browser".

>like it's done on mozilla addons

Firefox is dead now. Sad but true. Dead for me scince removing alsa support, subgrave for many others cause of removing XUL and all most of the addons in nearest future.
So, atm I'm traing to vake Chromium nore or less usable for myself.

 >You might need to

Ok, i'll check this way.

>Unsupported.

That's just to scare you off [1], the flag is supported by the browser but not by Google :-) and is required to let those manifest.json take effect

  [1]: https://cs.chromium.org/chromium/src/chrome/browser/ui/startup/bad_flags_prompt.cc?l=75&rcl=d6653466e313dc83a33ec049a6eef95a31dda435

As this is a feature request , marking this as untriaged for further inputs on this.

Thanks!

Archiving old bugs that haven't been actively assigned in over a year.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!