Repository navigation
Open w3bs:// URIs through the w3bs.org resolver - #149
Merged
Merged
Conversation
Chromium has no handler for w3bs://, so W3BS URIs now route to https://w3bs.org/browse?q=<uri> from every entry point: - launcher: `tron w3bs://...` args are rewritten to the gateway (TRONBROWSER_W3BS_GATEWAY overrides it) - desktop entries claim x-scheme-handler/w3bs; install.sh makes TronBrowser the default only when no other handler is set - bundled extension: w3bs-links.js turns clicks on w3bs: links into in-tab navigations (middle/modifier click opens a new tab), and the new-tab box treats a W3BS URI as an address in web and AI modes Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
ThreatCrush Security Scan48 finding(s) HIGH/CRITICAL: 2 | MEDIUM: 25 | LOW: 21
Snippets are redacted; ThreatCrush never prints matched credential material. |
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.
Chromium has no handler for
w3bs://, so TronBrowser now routes W3BS URIs tohttps://w3bs.org/browse?q=<uri>(the existing resolver page) from every entry point:tron w3bs://prompt/w3bs/research@1rewrites the arg to the gateway;TRONBROWSER_W3BS_GATEWAYoverrides it.x-scheme-handler/w3bs. install.sh sets TronBrowser as the default only when nothing else (e.g. the w3bs inspector) already handles it.w3bs-links.jsturns clicks onw3bs:links into in-tab navigations, so there is no xdg-open dialog (middle/modifier click opens a new tab). Same match patterns as the existing content scripts, so no new permissions. The new-tab box treats a W3BS URI as an address.Tested:
vitest runin apps/desktop: 157 passed, 4 skipped (new launcher +w3bs.test.jscases)sh -non the launcher and install.shq(HTTP 200, canonicalresearch@1.0.0)w3bs://link landed onw3bs.org/browse?q=w3bs%3A%2F%2Fprompt%2Fw3bs%2Fresearch%401Typing
w3bs://…in the omnibox still goes through Chromium's external-protocol prompt, then the desktop handler, then a new tab. Linux only; macOS/Windows scheme registration is not covered.🤖 Generated with Claude Code