Will adding externally_connectable to an existing extension manifest cause the extension to become disabled?

[Shaun Merritt]

Hi Everyone!

Hope you are all having a great holiday season and staying safe and healthy.

Our extension frequently communicates with our website by attaching event listeners to buttons through a content script injected on our site. We recently learned about the "externally_connectable" feature (found here: https://developer.chrome.com/docs/extensions/mv2/messaging/#external-webpage) which would make this much more reliable. I'm hesitant to modify our manifest file between releases given that it's not very clear what permission modifications specifically will disable an extension. Given this isn't a permission, but rather a feature, I'm curious if anyone has experienced releasing a similar update to their extension and if that caused your extension to become disabled?

I 100% understand and stand behind Googles decision to disable extensions that change permissions, but would love to hear if anyone has experience with modifying other aspects of the manifest file and how that impacts existing users. Thank you all so much! 

[Jackie Han]

"externally_connectable" field (and it's "matches" sub field) is not a warning permission. If you only add this one change, it should not be disabled.

Ref: https://developer.chrome.com/docs/extensions/mv2/permission_warnings/#permissions_with_warnings

You can also see permission warnings in your extension details page.

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/9947872b-88e0-4d90-b4ef-9d10738a6416o%40chromium.org.

--

韩国恺(Jackie)