Passing Messages in Extensions


Communicating and passing messages around is an essential part in developing extensions. Let’s take a look at the different ways to do that using the Opera Extensions API.

The two broad types of communication methods we have are simple short lived messages, and a more long lived communication method. We’ll cover both in this article.

Simple short lived communication

If all you need to do is to send a one-shot message to another part of the extension, and optionally get a callback, then you can use the runtime.sendMessage() or tabs.sendMessage() methods to do so. To receive a message, use the runtime.onMessage() method.

Let’s take an example of an extension which (on click of a button) counts the number of <p> elements in the page and updates the button with a badge showing the number.

In the background script, we initially write:

chrome.browserAction.onClicked.addListener(function() {
		currentWindow: true,
		active: true
	// Select active tab of the current window
	}, function(tab) {
			// Send a message to the content script
			tab[0].id, { line: 'countparas' }

So in effect, we are selecting the currently active tab of the current window and sending a message the content script associated with it. When the content script receives this message, it will initiate a function, like so:

	function (request, sender){
		// If we get the request from the Background script
		if (request.line == 'countparas'){
			// Select all `<p>` elements in the document body
			var paras = document.body.querySelectorAll('p');
			// If the number of `<p>` elements is greater than zero
			if (paras.length > 0) {
				// Assigning that number to a variable called 'theCount'
				// and convert it to a string format
				var theCount = paras.length + '';
				// Send the count back to the background script
				chrome.runtime.sendMessage({ count:theCount });
			} else {
				alert('There does not seem to be any `<p>` elements in this page!');

Here the content script is listening for the message countparas, and only once it receives it, it initiates the counting of all the <p> elements in the page. Once it does that, it sends back a message with the count.

The background script once again listens for a message from the content script regarding the count, and once it does, it updates the badge like so:

	function (request, sender) {
		// If there exists a value named 'count'
		// in the message sent by content script
		if (request.count) {
			console.log('Count of paragraphs in the document is: ' +
				request.count + 'and tab id is ' +;
			var mytext = '' + request.count + '';
			// Set the badge of the extension to the value of 'mytext'
			chrome.browserAction.setBadgeText({ text: mytext });

Cross-extension messaging

In addition to sending messages between different components in your extension, you can use the messaging API to communicate with other extensions. This lets you expose a public API that other extensions can take advantage of.

Listening for incoming requests and connections is similar to the internal case, except you use the runtime.onMessageExternal or runtime.onConnectExternal methods. Here’s an example of each:

// For simple requests:
	function(request, sender, sendResponse) {
		if ( == blacklistedExtension) {
			// Don’t allow this extension access
		} else if (request.getTargetData) {
			sendResponse({ targetData: targetData });
		} else if (request.activateLasers) {
			var success = activateLasers();
			sendResponse({ activateLasers: success });

// For long-lived connections:
chrome.runtime.onConnectExternal.addListener(function(port) {
	port.onMessage.addListener(function(msg) {
		// See other examples for sample onMessage handlers

Likewise, sending a message to another extension is similar to sending one within your extension. The only difference is that you must pass the ID of the extension you want to communicate with. For example:

// The ID of the extension we want to talk to
var laserExtensionId = '<sample extension id>';

// Make a simple request
chrome.runtime.sendMessage(laserExtensionId, { getTargetData: true },
	function(response) {
		if (targetInRange(response.targetData)) {
				laserExtensionId, { activateLasers: true }

// Start a long-running conversation
var port = chrome.runtime.connect(laserExtensionId);

Sending messages from web pages

Similar to cross-extension messaging, your app or extension can receive and respond to messages from regular web pages. To use this feature, you must first specify in your manifest.json which web sites you want to communicate with. For example:

"externally_connectable": {
	"matches": ["*://**"]

This will expose the messaging API to any page which matches the URL patterns you specify. The URL pattern must contain at least a second-level domain — that is, hostname patterns like **.com*, and * are prohibited. From the web page, use the runtime.sendMessage or runtime.connect APIs to send a message to a specific app or extension. For example:

// The ID of the extension we want to talk to
var editorExtensionId = '<sample extension id>';

// Make a simple request
chrome.runtime.sendMessage(editorExtensionId, { openUrlInEditor: url },
	function(response) {
		if (!response.success) {

From your app or extension, you may listen to messages from web pages via the runtime.onMessageExternal or runtime.onConnectExternal APIs, similar to cross-extension messaging. Only the web page can initiate a connection. Here is an example:

	function(request, sender, sendResponse) {
		if (sender.url == blacklistedWebsite) {
			// Don’t allow this web page access
		if (request.openUrlInEditor) {

Native messaging

Extensions can exchange messages with native applications. Native applications that support this feature must register a native messaging host that knows how to communicate with the extension. Opera starts the host in a separate process and communicates with it using standard input and standard output streams.

You need to declare the appropriate permission in the extension’s manifest file.

"permissions": [ "nativeMessaging" ]

Native messaging host

In order to register a native messaging host the application must install a manifest file that defines the native messaging host configuration. Below is an example of the manifest file:

	"name": "com.my_company.my_application",
	"description": "My Application",
	"path": "C:\\Program Files\\My Application\\chrome_native_messaging_host.exe",
	"type": "stdio",
	"allowed_origins": [

The native messaging host manifest file contains the following fields:

nameName of the native messaging host. Clients pass this string to runtime.connectNative or runtime.sendNativeMessage.
descriptionShort application description.
pathPath to the native messaging host binary. On Linux and OSX the path must be absolute. On Windows it can be relative to the directory in which the manifest file is located.
typeType of the interface used to communicate with the native messaging host. Currently there is only one possible value for this parameter: stdio. It indicates that Opera should use stdin and stdout to communicate with the host.
allowed_originsList of extensions that should have access to the native messaging host.

Location of the manifest file depends on the platform:

Windows: The manifest file can be located anywhere in the file system. The application installer must create registry key


and set default value of that key to the full path to the manifest file.

OSX: The manifest file must be placed at

~/Library/Application Support/Google/Chrome/NativeMessagingHosts/

Linux: The manifest file must be placed at


Opera starts each native messaging host in a separate process and communicates with it using standard input (stdin) and standard output (stdout). The same format is used to send messages in both directions: each message is serialized using JSON, UTF-8 encoded and is preceded with 32-bit message length in native byte order.

Other methods of communication

In some situations you might want a more persistent form of communication between the different parts of your extension, in which case you can open a message channel between your content script and the extension page using runtime.connect() or tabs.connect().

You can communicate between different extensions by using the runtime.onMessageExternal() and runtime.onConnectExternal() methods.