Skip to content

[BUG] Fix camera and microphone for video calls in Chromium tabs - #29

Merged
ignaciojuarez merged 2 commits into
mainfrom
t3/fix-chromium-camera-mic
Nov 10, 2026
Merged

ignaciojuarez merged 2 commits into
mainfrom
t3/fix-chromium-camera-mic

Conversation

@ignaciojuarez

Copy link
Copy Markdown
Owner

Problem

A Zoom link in a Chromium tab did not work. Three causes:

  1. Chromium never saw Cobble's Allow. After Allow, pages got permissions.query = prompt and unnamed devices with empty IDs from enumerateDevices. Zoom, Meet and Teams use both to choose a device, so they report no camera or microphone. The SDK harness reproduces this on the beta 14 runtime.
  2. A hidden sidebar refused prompts. Camera, microphone and screen sharing prompts point at the site control in the sidebar. With the sidebar hidden there was no anchor, so requests were denied without a prompt.
  3. macOS privacy denial was silent. A page whose camera/microphone access macOS blocked only got NotAllowedError.

Fix

  • Pin chrome-sdk#21 (77ab40e). Allow leaves a one-time grant, and the permission resolver answers camera and microphone too.
  • ChromiumEngine: the resolver maps camera/microphone to Cobble's saved decisions; resetPermission clears them. The site-menu switch, Settings and Forget now revoke Chromium's camera/microphone grants as well.
  • PagePresenter.revealSiteControl runs only when a prompt will actually ask. BrowserWindowModel then holds the sidebar visible and lays it out in the same pass, until the prompt resolves.
  • When macOS privacy blocks a device Cobble allowed, the window shows where to turn it on (English and Spanish).

Tests

  • New: UITests.testHiddenSidebarShowsTheSiteControlWhileAPromptIsPending, PagePresenterTests.testOriginPromptsRevealTheSiteControlOnlyWhenTheyAsk, PagePresenterTests.testSystemPrivacyBlockIsReportedOnlyForBlockedDevices.
  • The WebKit permission flow test now checks device names after a grant. The fixture gains a 1b. Devices step.
  • docs/features/screen-sharing.md now says what each test layer proves and cannot prove, and adds a manual release gate on real hardware: notarized build, TCC prompt, Zoom test meeting and Meet.

Validation

  • Full hosted suite (./Scripts/test.sh): 652 tests, 0 failures, 2 skipped. The two skipped tests press real prompts and need Cobble in the foreground.
  • swift build and adapter swift test (12) against pinned 77ab40e.
  • SDK harness on the rebuilt runtime: 256/256, including the new camera/microphone checks.

Not qualified

  • Real camera/microphone hardware.
  • A Developer ID/notarized Full build.
  • Real Zoom or Meet calls.
  • Clicking the real prompts in the foreground.

The maintainer Mac mini has no camera or microphone, so camera and microphone requests there end in NotFoundError regardless of Cobble.

🤖 Generated with Claude Code

ignaciojuarez and others added 2 commits November 10, 2026 11:43
Zoom, Meet and Teams could not use the camera or microphone in Chromium
tabs: after Allow, pages saw an unanswered permission and unnamed devices.

- Pin chrome-sdk 77ab40e, which records Allow as a one-time grant and lets
  Cobble's saved decisions answer camera/microphone status checks,
  permissions.query and enumerateDevices device details.
- Chromium's permission resolver and resets now cover camera and
  microphone, so turning a permission off or Forget clears Chromium's grant.
- Camera, microphone and screen sharing prompts show a hidden sidebar
  instead of being refused without asking.
- When macOS privacy blocks Cobble from the camera or microphone, allowing a
  site says where to turn it on.
- Tests: hidden-sidebar anchor, reveal only when asking, privacy-block
  detection, and device names after a WebKit grant. The permission fixture
  gains a devices step. docs/features/screen-sharing.md lists what each test
  layer proves and a manual release gate on real hardware.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ignaciojuarez
ignaciojuarez merged commit c51a7e7 into main Nov 10, 2026
1 check passed
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