Provide browser-specific help with audio/video device settings
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 2.2k
- Forks
- 587
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
Something I heard from partners, about Talk. They weren't using Talk for calls with prospects, because they had to help them often with using Talk. The prospects, often not very technical, would click away the permissions dialog and where some other solutions then show screenshots or an image or arrow on with where to click to give permission, depending on the browser, Talk does not - leaving them to ask what browser is being used and then guide the user through chat to give permission. We can do better, detecting the browser and showing the user how to do it.
This is probably a number of separate improvements - just providing this here as @jancborchardt asked me to.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating Talk's audio/video permission handling and browser detection entry points, then review the existing user-facing permission flow. Done means users who dismiss permissions receive browser-specific guidance for restoring microphone and camera access.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- audio-video-rtc, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100