fix: handle file:// URLs in navigate and close-tabs tools#305
Open
nklyshko wants to merge 1 commit intohangwin:masterfrom
Open
fix: handle file:// URLs in navigate and close-tabs tools#305nklyshko wants to merge 1 commit intohangwin:masterfrom
nklyshko wants to merge 1 commit intohangwin:masterfrom
Conversation
chrome.tabs.query requires valid Chrome match patterns (e.g. https://example.com/*). The pattern-building logic unconditionally extracted host + path-wildcard, but file:// URLs have no host — producing broken patterns like file:///home/* that never match any open tab. For file:// URLs, use the exact URL as the query pattern instead, which Chrome supports and correctly identifies the specific local file. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
1 participant
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.
chrome.tabs.query requires valid url match patterns (e.g.
https://example.com/*). The pattern-building logic unconditionally extracted host + path-wildcard, but file:// URLs have no host — producing broken patterns like file:///home/* that never match any open tab.For file:// URLs, use the exact URL as the query pattern instead, which Chrome supports and correctly identifies the specific local file.