Troubleshooting
Firefox versus Chrome: the differences that matter
Same features, same detectors. The differences are in where you install from, private windows, permission prompts, and site access controls.
Updated
The extension is one codebase built for both browsers under Manifest V3. Detection, the circle, the card, the popup and the options page behave the same. What differs:
| Chrome and Chromium browsers | Firefox | |
|---|---|---|
| Install source | Chrome Web Store | Firefox Add-ons (desktop Firefox 128+) |
| Permission prompt | One prompt on install | A permission prompt plus a data-collection notice listing what the add-on may send |
| Private windows | Allow in the extension's details page | Asked at install, or in about:addons under Run in Private Windows |
| Site access controls | Site access menu on the extensions page (all sites, specific sites, on click) | Permissions tab in about:addons |
| Settings sync | Chrome sync | Firefox Sync |
| Session storage for hidden posts | chrome.storage.session |
Firefox equivalent, cleared when the browser closes |
Things that are the same
The API it talks to, what it sends, the daily limits, the Pro gating, the built-in exclusion of slopsquash.com, and the connect page flow. Each browser needs its own connection and gets its own 90-day token.
Things that are not supported anywhere
Safari, mobile browsers other than desktop-class Chromium builds that accept Web Store extensions, and browser-native pages and PDF viewers.
Reporting a browser-specific problem
Say which browser and version in the email; see Report a site that does not work.