Path: blob/main/files/en-us/mozilla/add-ons/webextensions/api/runtime/connect/index.md
6552 views
------{{AddonSidebar()}}
Make a connection between different contexts inside the extension.
You can call this:
in an extension's content scripts, to establish a connection with the extension's background scripts (or similarly privileged scripts, like popup scripts or options page scripts).
in an extension's background scripts (or similarly privileged scripts), to establish a connection with a different extension.
Note that you can't use this function to connect an extension to its content scripts. To do this, use {{WebExtAPIRef('tabs.connect()')}}.
By default, this connection enables the extension to exchange messages with itself or any other extension (if extensionId is specified). However, the externally_connectable manifest key can be used to limit communication to specific extensions and enable communication with websites. Connections within the extension trigger the {{WebExtAPIRef('runtime.onConnect')}} event, connections from other extensions or web pages trigger the {{WebExtAPIRef('runtime.onConnectExternal')}} event.
Syntax
Parameters
extensionId{{optional_inline}}:
string. The ID of the extension to connect to. If the target has set an ID explicitly using the browser_specific_settings key in manifest.json, thenextensionIdshould have that value. Otherwise it should have the ID that was generated for the target.
connectInfo{{optional_inline}}:
object. Details of the connection:name{{optional_inline}}:
string. Will be passed into {{WebExtAPIRef("runtime.onConnect")}} for processes that are listening for the connection event.
includeTlsChannelId{{optional_inline}}:
boolean. Whether the TLS channel ID will be passed into {{WebExtAPIRef("runtime.onConnectExternal")}} for processes that are listening for the connection event.
Return value
{{WebExtAPIRef('runtime.Port')}}. Port through which messages can be sent and received. The port's onDisconnect event is fired if the extension does not exist.
Browser compatibility
{{Compat}}
Examples
This content script:
connects to the background script and stores the
Portin a variable calledmyPort.listens for messages on
myPortand logs them.sends messages to the background script, using
myPort, when the user clicks the document.
The corresponding background script:
listens for connection attempts from the content script.
when it receives a connection attempt:
stores the port in a variable named
portFromCS.sends the content script a message using the port.
starts listening to messages received on the port, and logs them.
sends messages to the content script, using
portFromCS, when the user clicks the extension's browser action.
{{WebExtExamples}}
Note: This API is based on Chromium's
chrome.runtimeAPI. This documentation is derived fromruntime.jsonin the Chromium code.