One-click Zoom cookie cleanup for Error 1132.
Clears Zoom cookies and this tab's Zoom site data, then reloads the current Zoom tab.
One shared implementation. Independently packaged for Chrome, Edge, Brave, and Firefox, plus a BRAVIA TV guide.
Visit Website • Feedback & Report • Privacy Policy • Windows App
This is the canonical public source for the 1132 Fixer browser extension. Issues, pull requests, and CI live here. Companion products: Windows and macOS.
Independent project. Not affiliated with Zoom Video Communications, Inc.
When the active tab is on zoom.us, zoom.com, or a subdomain, the popup shows ZOOM DETECTED
and one FIX ZOOM button. After you press it, and only then, the extension:
- Deletes cookies for
zoom.usandzoom.com, including subdomains and partitioned cookies. - Clears this tab's Zoom-origin
localStorage,sessionStorage, Cache API, and IndexedDB with a one-shot, origin-checked injected function. - Reloads the active Zoom tab.
- Reports a cookie count and whether the tab's site data was cleared. Values are never shown.
On any other page the popup shows NOT ZOOM and no button. If the browser has revoked the extension's Zoom site access, it shows ACCESS NEEDED and asks for it when you press FIX ZOOM.
It reports the operation result. It does not detect Error 1132 and cannot verify that Zoom recovered. If the error survives a browser cleanup, use the Windows app.
| Target | Package | Runtime status | Notes |
|---|---|---|---|
| Google Chrome | release/chrome/1132-fixer-chrome-<v>.zip |
Automated behaviour tests (Chromium) and install smoke; branded Chrome manual | Base manifest. Chrome Web Store listing exists (older version). |
| Microsoft Edge | release/edge/1132-fixer-edge-<v>.zip |
Install smoke in Chromium; branded Edge manual | Own store identity for Edge Add-ons. Not yet listed. |
| Brave | release/brave/1132-fixer-brave-<v>.zip |
Install smoke in Chromium; branded Brave manual | Brave users install the Chrome Web Store package. |
| Mozilla Firefox | release/firefox/1132-fixer-firefox-<v>.zip |
Automated behaviour tests in real Gecko; web-ext lint; extension install manual |
Own Gecko id, Firefox 140+, built-in data-collection consent for bug reports. AMO signing is manual. |
| Sony BRAVIA Professional Displays | release/bravia/1132-fixer-bravia-<v>.zip |
Emulated at TV viewports; physical display validation required | A ten-foot guide client for Sony's HTML5 runtime. The extension cannot run on a TV. |
| Sony BRAVIA consumer TVs | none | Unsupported | No extension runtime. |
| Safari | none | Not implemented | Path documented in docs/platforms/safari.md. |
Full matrix with status vocabulary: docs/platforms/compatibility-matrix.md.
git clone https://github.com/1132-Fixer/browser.git
cd chrome
npm ci
npx playwright install chromium firefox
npm run check # lint, typecheck, unit, build, manifests, permissions, integration, package, packages, e2eLoad a build unpacked: npm run build:chrome, then chrome://extensions → Developer mode → Load
unpacked → dist/chrome. Firefox: npm run build:firefox, then about:debugging → Load Temporary
Add-on → dist/firefox/manifest.json. Windows helper: install.bat opens the Chrome extensions
page and the dist/chrome folder.
apps/extensions/{chrome,edge,brave,firefox} manifest (base or overlay) + shipped README per target
apps/tv/bravia BRAVIA TV guide client + Sony launcher package
packages/core the one cleanup implementation (no browser namespace)
packages/browser-api feature-detected adapter over browser.* / chrome.*
packages/ui popup and report pages, icons
packages/platform-types, packages/test-utils shared types; recording namespace mock for tests
tooling/{build,packaging,release,store-assets} build, zip, verify, bump, store assets
tests/{unit,integration,end-to-end} node:test, source/build guards, Playwright suites
docs/ architecture, research, platforms, security, testing, release
Details: docs/architecture/repository-layout.md.
| Command | What it does |
|---|---|
npm run dev:<target> |
Build one target and rebuild on change (chrome, edge, brave, firefox, bravia). |
npm run build / build:<target> |
Write dist/<target>/. |
npm run package / package:<target> |
Zip dist/<target>/ into release/ with SHA-256 sums. |
npm run lint |
Source guards: Zoom-only, one browser boundary, nothing before FIX ZOOM, no telemetry or remote code, approved claim, no secrets. |
npm run typecheck |
Strict TypeScript check. |
npm test |
Unit + integration (needs a build for integration). |
npm run test:e2e |
Playwright matrix: Chromium, Firefox, extension install smoke, BRAVIA client. |
npm run verify:manifests / verify:permissions / verify:packages |
Generated manifests (+ web-ext lint), permission justifications, release zips. |
npm run check |
Everything, in CI order. |
npm run bump |
Patch version everywhere (never hand-edit versions). |
npm run assets |
Chrome Web Store screenshots and promo images. |
| Permission | Why |
|---|---|
cookies |
Find and remove Zoom cookies. |
activeTab |
Read the active tab's URL when the popup opens; reload it after the cleanup. |
scripting |
Inject the one-shot, origin-checked cleaner into the active Zoom tab after FIX ZOOM. |
zoom.us / zoom.com hosts (http and https) |
Limit cookie access and injection to Zoom. |
No <all_urls>, browsingData, tabs, history, background worker, content scripts, telemetry, or
remote code. Every permission is justified per target in
docs/security/permissions-matrix.md and CI fails if a new one
appears without a justification.
npm run check is green locally and in CI on every push: source guards, strict type-check, unit
tests, five builds, generated-manifest validation with web-ext lint, permission justifications,
build integration checks, five release zips, package validation, and six end-to-end suites
(Chromium and Firefox popup and report, Chromium install smoke for Chrome / Edge / Brave, BRAVIA at
three TV viewports). What remains manual is listed in
docs/testing/README.md and docs/known-limitations.md.
- Architecture overview and decision records
- Primary-source research
- Platforms: Chrome, Edge, Brave, Firefox, BRAVIA, Safari
- Security: threat model, permissions matrix
- Testing
- Release: packaging, store preparation, Firefox signing
- Migration from the flat layout, troubleshooting, known limitations
The fix flow makes no network request. The optional Report-a-Bug page is the only networked surface; it sends only what you type and attach, only when you press Submit, to the project's support service. Full text: PRIVACY_POLICY.md.
Code, documentation, and design tokens: MIT. The 1132 Fixer product names, logo, icons, and brand artwork are not covered by the MIT licence; see TRADEMARKS.md, ASSET-LICENSE.md, and NOTICE.md.
