Replies: 1 comment
-
Hi @gdh1995, thank you for bringing it up. I will check with our Engg team for solutions/possibilities & get back to you. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I once made a general extension and I want to make it run on all tabs including extension pages (e.g. a PDF viewer extension can support another VIM-like keyboard-shortcut extension), but MV3's
content_security_policy.extension_pages
is so strict that my trick on MV2 breaks. So I wonder whether Edge team can update MV3 policy to re-enable this usage.Sorry to disturb you, but although I've filed https://bugs.chromium.org/p/chromium/issues/detail?id=1282890 on Dec 27, 2021, there seem no people to take care about it. In fact I haven't seen any outside non-crash issue being solved by the Google Chromium team.
The details of my trick in MV2 is:
manifest.json
declares a speical CSP, like:"content_security_policy": "script-src 'self' chrome-extension://hfjbmagddngcpeloejdejnfgbamkjaeg/; object-src 'self'"
<script src="chrome-extension://hfjbmagddngcpeloejdejnfgbamkjaeg/lib/injector.js"></script>
lib/injector.js
is also written by myself, and it will send messages, inject other<script>
elementshfjbmagddngcpeloejdejnfgbamkjaeg
runs perfectly on the prior extensionMy Vimium C has been accepted to run on 6 extensions published on Chrome Web Store, and 4 is made by myself while 2 are other extensions which have hundreds of thousands of users (SalaDict and Edge Translate). The version of Vimium C for Edge Add-Ons has 47K+ users and also support this usage.
However, Google's MV3 doesn't allow the
chrome-extension:
protocol incontent_security_policy.extension_pages
, and then my trick breaks. I can not understand why it even allowshttp://localhost:<port>
(as said here) but insist on refusing other extensions' scripts . I appreciate contributions of you Edge team if anyone can help and addchrome-extension:
back.Notes:
CSP
rules, an extension can run scripts from any other extension if only it knows script URLs (there's a random extension UUID in URL generated on first installation).Beta Was this translation helpful? Give feedback.
All reactions