Connecting without externally_connectable #
externally_connectable is not declared in your extension's manifest, all extensions and apps can connect, but no webpages can connect. As a consequence, when updating your manifest to use
"ids": ["*"] is not specified then other extensions and apps will lose the ability to connect to your extension. This may be an unintended consequence, so keep it in mind.
Sample manifest.json #
"name": "My externally connectable extension",
// Extension and app IDs. If this field is not specified, no
// extensions or apps can connect.
// Alternatively, to match all extensions and apps, specify only
// Match patterns for web pages. Does not affect content scripts.
// If this field is not specified, no webpages can connect.
// Indicates that the extension would like to make use of the TLS
// channel ID of the web page connecting to it. The web page must
// also opt to send the TLS channel ID to the extension via setting
// includeTlsChannelId to true in runtime.connect's connectInfo
// or runtime.sendMessage's options.
The externally_connectable manifest key can have the following properties:
ids(array of string) - optional
The IDs of extensions or apps that are allowed to connect. If left empty or unspecified, no extensions or apps can connect.
"*"will allow all extensions and apps to connect.
matches(array of string) - optional
The URL patterns for web pages that are allowed to connect. This does not affect content scripts. If left empty or unspecified, no web pages can connect.
Patterns cannot include wildcard domains nor subdomains of (effective) top level domains;
http://*.chromium.org/*are valid, while
*://*.com/*, and even
accepts_tls_channel_id(boolean) - optional
true, messages sent via runtime.connect or runtime.sendMessage will set runtime.MessageSender.tlsChannelId if those methods request it to be. If
false, runtime.MessageSender.tlsChannelId will never be set under any circumstance.