Skip to content

Instantly share code, notes, and snippets.

@alexstrat
Last active April 2, 2020 10:53
Show Gist options
  • Star 6 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save alexstrat/0bc561e769664fc9ab520b73c0a2dd2c to your computer and use it in GitHub Desktop.
Save alexstrat/0bc561e769664fc9ab520b73c0a2dd2c to your computer and use it in GitHub Desktop.
Chrome extensions support in Electron

Here is a list of blockers I stumbled upon while trying to run some Chrome extensions in Electron.

Description Reference on electron repo Extensions blocked
Add API to load extensions independent of devToolsExtensions pull#9918 all
content_scrips support: support CSS in pull#10076* Mailtracker Grammarly
content_scrips support: fix matches rules implementation in pull#10075* Mailtracker
content_scrips support: run JS scripts in same context in pull#9494* (closed) Mailtracker Grammarly
Fix insecure content error for resources load via chrome-extension: pull#9950 Mailtracker
Add support for chrome.runtime.getManifest() Grammarly
content_scrips support: fix chrome.storage to access extension data independently of host page's doamain Reported in #9949 fixed in #9951 Mailtracker
Fix page's URL used to test against content_scripts[].matches pull#9953 (merged) Mailtracker
[for security] Option to run content_scripts only in webviews

* workaround with repackage-chrome-extension-for-electron

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment