Skip to content

Support Firefox via engine-aware channel routing - #9

Open
vc0d35 wants to merge 1 commit into
mainfrom
feature/firefox-support
Open

Support Firefox via engine-aware channel routing#9
vc0d35 wants to merge 1 commit into
mainfrom
feature/firefox-support

Conversation

@vc0d35

@vc0d35 vc0d35 commented Sep 3, 2026

Copy link
Copy Markdown
Owner

Firefox's ICE stack refuses to dial loopback candidates, so loopback ports

= 1024 fall back to fetch (which on Firefox resolves for any open port, not
just HTTP); LAN and remote high ports still use ICE as on Chromium. The open oracle now keys on candidate-pair state (in-progress/succeeded), which both engines populate, instead of the Chromium-only requestsSent.

  • batch.js: isChromium() + isLoopbackHost() gate the ICE/fetch split
  • probeWithIce.js: unified state-based oracle
  • tests: mock emits state; new loopback-fallback case; ICE-routing tests use a non-loopback host; e2e runs Firefox with loopback-ICE specs gated to Chromium; CI installs Firefox
  • README: three-way per-engine routing, oracle, and caveats

Signed-off-by: v_c0d35 <vini.andrade.dev@gmail.com>
@vc0d35
vc0d35 force-pushed the feature/firefox-support branch from 121df8a to 2c50768 Compare September 3, 2026 14:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant