What’s new in Chrome 116 for Extensions

# Programmatically open a Sidepanel

Sidepanel has been one of the most requested features in Chrome extensions and has been available in Chrome since version 114. After launching the Side Panel API, one of the first pieces of feedback that we’ve received was that developers want a way to programmatically open a side panel. And here it is: chrome.sidePanel.open is now in beta. You can use it to open the extension side panel programmatically in response to a user interaction, such as a context menu click:

chrome.contextMenus.onClicked.addListener((info, tab) => {
if (info.menuItemId === 'openSidePanel') {
// This will open the panel in all the pages on the current window.
    chrome.sidePanel.open({ windowId: tab.windowId });
}
});

# WebSocket support in Service Workers

WebSocket support is critical for many extensions planning to move to Manifest V3. Chrome 116 further improves WebSocket support in service workers as all WebSocket activity will reset the 30s service worker idle timer. This means that as long as your WebSocket is active, the service worker will stay alive.

You can use this to implement a keepalive mechanism ensuring your service worker stays active while you’re waiting for messages from your server – even if it takes more than 30s until the next message arrives:

function keepAlive() {
const keepAliveIntervalId = setInterval(
() => {
if (webSocket) {
        webSocket.send('keepalive');
} else {
clearInterval(keepAliveIntervalId);
}
},
// It's important to pick an interval that's shorter than 30s, to
// avoid that the service worker becomes inactive.
20 * 1000
);
}

Check out our new WebSocket guide and sample for more details.

# Strong keepalive for Service Workers

Speaking of service worker lifecycle, another important update has landed: strong keepalive for APIs requiring user interaction. APIs that require a user interaction will have “strong” keepalives for extension service workers (i.e., allow the worker to take longer than 5 minutes on this task):

• permissions.request()
• desktopCapture.chooseDesktopMedia()
• identity.launchWebAuthFlow()
• management.uninstall()

# Recording audio and video in the background

Another gap between Manifest V2 and Manifest V3 has been closed: you can record audio and video in the background using tabCapture and offscreen documents. Use the chrome.tabCapture API in a service worker to obtain a stream ID following a user gesture. This can then be passed to an offscreen document to start recording.

Check out our updated tabCapture guide to learn how it works or, for a working example, see the Tab Capture – Recorder sample.

# New API: runtime.getContexts()

The new runtime.getContexts() API lets you fetch information about active contexts associated with your extensions. For example, you can use it to check if there is an active offscreen document:

const existingContexts = await chrome.runtime.getContexts({});
const offscreenDocument = existingContexts.find(
(c) => c.contextType === 'OFFSCREEN_DOCUMENT'
);

# New offscreen reason: GEOLOCATION

geolocation has been added as another valid reason for using an offscreen document. Check out our guide using geolocation to learn more about how to obtain the geographical location of the extension using the Offscreen API.

# chrome.action.setBadgeText()

action.setBadgeText has been updated to address an inconsistency between Manifest V2 and Manifest V3. Passing an empty string or null to action.setBadgeText will clear the badge text for the specified tab and default to the global badge text instead.

action.setBadgeText({tabId: tabId, text: ''});

# Summary: another step towards Manifest V3

With improved Service Worker lifetime support and the updated TabCapture API we’ve continued to make progress on our goal to close the feature gap between Manifest V2 and V3. Checkout our known issues page for the current status.