Repository navigation
[BUG] Let sites list and pick cameras and microphones after Allow - #21
Merged
Merged
Conversation
After the host allowed camera or microphone, Chromium kept no record of it: permissions.query reported "prompt" and enumerateDevices returned unnamed devices with empty IDs, so meeting sites such as Zoom and Meet reported no camera or microphone. - The host's permission resolver now also answers camera and microphone status checks (patch 0040), so saved decisions hold for quiet checks, permissions.query and device details. - An allowed request leaves a one-time grant for the top-level origin, like Chrome's "Allow this time". - CCSContextResetPermission and ChromiumContext.resetPermission clear camera and microphone grants too. - Five new harness checks cover device details after Allow, picking a device by ID, reset, and saved allow/deny. The beta 14 runtime fails the first. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ignaciojuarez
added a commit
that referenced
this pull request
Nov 10, 2026
The camera/microphone device checks (#21) grew the harness's single async validation function past what the macOS CI runner can compile: the Swift frontend was killed (signal 9) and main's native-client check is red. Move three self-contained sections out of `run` without changing them: media/display/window-management requests, prompts/file choosers, and the new device checks (HarnessMediaDeviceValidation.swift). A clean local build's peak frontend memory drops from 26.6 GB to 15.9 GB, and build time from 156 s to 52 s. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
After Cobble allowed camera or microphone, Chromium kept no record of the decision. Pages then saw:
permissions.query({name: "camera"})→promptenumerateDevices()→ unnamed devices with empty IDsMeeting sites (Zoom, Meet, Teams) read both to choose a device, so they reported no camera or microphone. A new harness check reproduces this on the beta 14 runtime (
93c1dad): after Allow, the page reportedprompt prompt false false.Fix
MediaStreamDevicePermissionContextasks an embedder resolver first, as window management already does. The host'spermissionResolvernow answers camera and microphone with the top-level origin, so saved allow/deny hold for quiet checks,permissions.queryand device details.getUserMediacall still asks the host.CCSContextResetPermission/ChromiumContext.resetPermissionaccept.cameraand.microphone.Validation
python3 -m unittest(73),node Tests/test_smoke_fixture.mjs,swift test(34) andswift build --product CobbleChromiumClientpass.Not qualified
Fake devices skip macOS camera/microphone permission (TCC). Real hardware, a Developer ID release and real meeting sites still need manual checks.
release_ready: false.🤖 Generated with Claude Code