Very WIP! Not ready for release. Expect many bugs. Please don't sign builds on AMO with current ID.
Credit:
- Linux
- macOS (TODO)
- Windows (TODO)
Only tested on Linux. mDNS library issue to be fixed. mdns only works on Windows, mdns-js only works on Linux.
- NodeJS
nodebinary in pathBonjour SDK (Windows)
git clone https://github.com/hensm/caster.git
npm install
npm run buildInstaller scripts aren't written yet, so registering the native messaging manifest with Firefox and specifiying the path must be done manually:
MDN: Native Manifests
path key within app/caster_bridge.json must be set to absolute path of app/src/launcher.sh or app/src/launcher.bat. Then, the manifest must be either moved to the correct location or the path added to the registry (Windows):
MDN: Native Manifests # Manifest location
Testing requires geckodriver (or chromedriver for Chrome parity testing). See selenium-webdriver installation instructions (ignore npm install).
Chrome doesn't load the media router in a temporary selenium profile, so there's a bundled profile (test/ChromeProfile.zip). Extract the folder within as test/ChromeProfile/.
npm run build
npm test
SELENIUM_BROWSER=chrome npm testExtension can be loaded from about:debugging as a temporary extension.
Most sites won't load the cast API unless the browser presents itself as Chrome. The plan is to spoof the user agent string for a whitelist of cast-enabled sites, but that isn't implemented yet. You can workaround this by setting it manually or using a third-party extension.
HTML5 media elements have a "Cast..." context menu item that triggers a sender application. Only works on remote (non-local) media that isn't DRM-encumbered.
Cast-enabled websites will load the sender API shim and display a cast button as in Chrome, provided there are no bugs/incompatibilities with the shim.
Netflix / HTML5:
