Restrict page→content bridge to set-speed only#1463
Merged
Conversation
igrigorik
force-pushed
the
claude/fix-message-bridge-security-PTzEv
branch
from
March 28, 2026 02:07
495f1cf to
7ae9aa1
Compare
The message bridge now accepts exactly one page→content verb: `set-speed` with a validated, clamped numeric value. All persistent settings writes go through trusted extension contexts (options page, popup, background) which have direct chrome.storage access. StorageManager.set() in page context routes only lastSpeed through the bridge; other keys stay in-memory only.
igrigorik
force-pushed
the
claude/fix-message-bridge-security-PTzEv
branch
from
March 28, 2026 02:08
7ae9aa1 to
1183e60
Compare
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
2 participants
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.
The message bridge now accepts exactly one page→content verb:
set-speedwith a validated, clamped numeric value. All persistentsettings writes go through trusted extension contexts (options page,
popup, background) which have direct chrome.storage access.
StorageManager.set() in page context routes only lastSpeed through the
bridge; other keys stay in-memory only.