Repository navigation
Explain a blocked camera or microphone, and resume when it's allowed - #1505
Merged
Merged
Conversation
…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>
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.
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.
watchPermissionlistens 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.[formatted]strings atui.output.permission.blocked.*, translated into all locales.+layoutmoves 4.24 → 4.25MB, for the four en-US strings every page carries. The note is inimportGraph.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
Amplitudeexample with a faked blocked microphone:permissions.test.tscovers the browser detection table and the watcher. That includes reporting a change and never listening once stopped.npm run check:now,npm run test:run,npm run locales.Checklist
🤖 Generated with Claude Code