This is a backport PR for branch 45-x-y
#55283: fix: extension code drift
Merged
Created: Oct 23, 2026, 12:51:38 PM
Merged: Oct 23, 2026, 3:31:19 PM
1 comments
Target: 45-x-y
Description of Change
Backport of #55155
See that PR for details. Two of its fixes are left out because Chromium 156 cannot support them:
- the
chrome.cookies.getAllCookieStores()crash fix: the cookies API is not in//extensionsin this Chromium version navigator.clipboardin extension service workers: the Chromium feature is off by default here and has no browser-side hook
Checklist
- I have built and tested this change
- I have filled out the PR description
- I have reviewed and verified the changes
-
npm testpasses - tests are changed or added
- relevant API documentation, tutorials, and examples are updated and follow the documentation style guide
- PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, past tense, and no longer than 80 characters.
Release Notes
Notes:
- Fixed extension
chrome.webRequestevents reporting atabIdof-1andchrome.declarativeNetRequestrules restricted to tabs never matching. - Fixed
session.clearStorageData()unregistering the service workers of loaded extensions. - Fixed
chrome.managementmethods and events being unavailable to extensions with themanagementpermission. - Fixed
__MSG_*__placeholders not being localized in extension stylesheets. - Fixed extension service workers being stopped after 30 seconds while a WebSocket was active.
- Fixed sandboxed extension pages being hosted in a process with extension API privileges.
- Fixed extension service workers running an outdated script after an app restart when the extension's files changed without a version change.
- Fixed
chrome.alarmsand content scripts registered withpersistAcrossSessionsnot persisting across app restarts.
Backport Information
Backported from
#55155: fix: extension code driftOriginal PR Author
samuelmaddockOriginal PR Status
Merged
Original PR Merged At
Oct 23, 2026, 12:41:54 PM
Original PR Link
View on GitHubSemver Impact
Major
Breaking changes
Minor
New features
Patch
Bug fixes
None
Docs, tests, etc.
Semantic Versioning helps users understand the impact of updates:
- Major (X.y.z): Breaking changes that may require code modifications
- Minor (x.Y.z): New features that maintain backward compatibility
- Patch (x.y.Z): Bug fixes that don't change the API
- None: Changes that don't affect using facing parts of Electron