Skip to content

Explain a blocked camera or microphone, and resume when it's allowed - #1505

Merged
amyjko merged 1 commit into
mainfrom
permission-blocked-help
Nov 15, 2026
Merged

amyjko merged 1 commit into
mainfrom
permission-blocked-help

Conversation

@amyjko

@amyjko amyjko commented Nov 15, 2026

Copy link
Copy Markdown
Collaborator

Context

Once a browser has blocked the site's camera or microphone (an explicit Block, or Chrome's lockout after three dismissals), it refuses at once and stops asking. The denial's Retry button then appears to do nothing, and its explanation only said "allow it in your browser's settings". Even someone who found the setting got no response until they pressed Retry or reloaded.

  • Says what's true. While a denial shows, the stage asks the browser whether the permission is blocked. If it is, the explanation is replaced with where this browser keeps the setting: Chromium, Safari on a Mac/iPhone/iPad, Firefox, or a general fallback.
  • Resumes by itself. watchPermission listens for the permission-change event, so allowing it in site settings starts the project with no click. Retry stays visible, because Safari may not report the change.
  • Strings: four new [formatted] strings at ui.output.permission.blocked.*, translated into all locales.
  • Changelog: a new 0.42.0 entry, with the release's changelog translations.
  • Import budget: +layout moves 4.24 → 4.25MB, for the four en-US strings every page carries. The note is in importGraph.test.ts.

Not done: I suspect that in Chrome, clicking away from the prompt leaves the request pending, so the start gate sits there with no Retry. That needs a hand check before it's worth a timeout.

Related issues

Verification

  • Headless Chromium, using the Amplitude example with a faked blocked microphone:
    • After Start, the stage showed the Chromium steps.
    • Switching the fake to granted cleared the denial and started the project with no click.
  • Unit tests: permissions.test.ts covers the browser detection table and the watcher. That includes reporting a change and never listening once stopped.
  • Checks: npm run check:now, npm run test:run, npm run locales.

Checklist

  • Manual: Chrome dismiss once (Retry asks again), dismiss three times or Block (steps show, and allowing in site settings resumes the project), Safari, Firefox
  • Manual: whether the gate hangs after clicking away from Chrome's prompt
  • VoiceOver read of the blocked explanation

🤖 Generated with Claude Code

…1476)

Once a browser blocks the site, Retry can no longer bring its prompt back,
and the denial only pointed at "your browser's settings". The stage now
asks the browser whether the permission is blocked, shows where this
browser keeps the setting, and watches the permission so the project
starts by itself once it is allowed. Retry stays as the fallback for
browsers that don't report the change.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@amyjko
amyjko merged commit 7aa6c3f into main Nov 15, 2026
17 checks 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.

Explain how to enable microphone input for Volume()

1 participant