Optimize content script URL permissions - #29
Closed
nisargkolhe wants to merge 1 commit into
Closed
Conversation
Co-authored-by: nisargkolhe <nisargkolhe@gmail.com>
|
Cursor Agent can help with this pull request. Just |
nisargkolhe
deleted the
cursor/optimize-content-script-url-permissions-gemini-3-pro-preview-13a5
branch
December 5, 2025 14:13
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.
Update content script permissions to
http://*/*andhttps://*/*to follow the principle of least privilege.The spotlight content script only needs to run on regular web pages, as restricted URLs are already handled by a fallback mechanism in
background.js. This change improves privacy and security without impacting functionality.