feat: make Chrome extensions work on custom protocols#50588
Merged
Conversation
6 tasks
dd984bf to
c003c12
Compare
Member
|
Backport was approved in the Releases WG meeting on 4/1/2026. |
dsanders11
approved these changes
Apr 3, 2026
|
Release Notes Persisted
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of Change
Manual backport of #49951
See that PR for details.
Includes the follow-up fix from #50551.
Excludes the test changes to
spec/api-web-request-spec.tsbecause those tests relied on #45915.Also backports https://crrev.com/c/7639311 because #49951 relied on it.
Checklist
npm testpassesRelease Notes
Notes: Added
allowExtensionsprivilege toprotocol.registerSchemesAsPrivileged()to enable Chrome extensions on custom protocols.