Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Poor experience if camera/mic blocked #365

Open
ddfridley opened this issue May 12, 2023 · 0 comments
Open

Poor experience if camera/mic blocked #365

ddfridley opened this issue May 12, 2023 · 0 comments
Labels

Comments

@ddfridley
Copy link
Contributor

If the user blocks the camera / mic on visiting a recorder page, there is only a not suppored here message.

  1. User navigator.permissions to figure out the current permissions - before getting the camera
  2. If permission has already been allowed - then go ahead
  3. If permission has been blocked, pop up a dialog box that explains that to use this page they will need to allow the mic/and camera
    3a. figure you what browser they are using, and give them specific instructions on how to allow the mic camera. For chrome - see if you can open a tab to chrome://settings/content/siteDetails?site=https%3A%2F%2Fundebate-qa.herokuapp.com%2F&search=permission where the can set the permissions. (make sure to use the hostname to calculate the right path.
  4. If permission is set to ask, show a dialog telling the user they are going to be asked for permission to use the camera and microphone.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant