-
Notifications
You must be signed in to change notification settings - Fork 3
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
Have to allow mic permissions for each video page #27
Comments
Appears that this is a browser specific problem. One solution is to include documentation on how to set browser settings to avoid this problem. Not sure if there's an app-solution to this problem. |
There's nothing we can do in-app for this. Each browser lets you make exceptions that grant mic permissions to an entire website. For Chrome, see: https://support.google.com/chrome/answer/2693767?p=ib_access_cam_mic&rd=1 |
It's under the advanced settings, manage exceptions hyperlink which leads to another help page. I sent it to our sponsor with some comments, my hope is she can get it working. |
The other thing to consider is that most people don't WANT to grant blanket On Wed, Mar 19, 2014 at 1:58 PM, Jason Nelson notifications@github.comwrote:
|
It may be possible to refactor the mic code so it only asks for permission once per run. I think it will involve some J query finagling, but I can look at it tomorrow. |
That's essentially what the problem is. Accepting it once might not be so bad, but it asks for it every time a video page is loaded, and our sponsor feels this ruins the simulation part of the simulated conversation. |
I have it working so it only asks you once per conversation. I need to do some cleanup before I push it but it seems like this is the best fix for this issue. |
Great! I'll pull it after you push it, test it, and we'll see about getting it on ARC. Date: Thu, 20 Mar 2014 12:45:10 -0700 I have it working so it only asks you once per conversation. I need to do some cleanup before I push it but it seems like this is the best fix for this issue. — |
Ok, it's pushed, still needs some general cleanup, but to a user it should work as before, but without the constant loading of the recorder |
I just tried it out on Firefox and on OperaNext, and I only got the message the first time. I'm prepared to say this issue is resolved, pending code cleanup. |
No description provided.
The text was updated successfully, but these errors were encountered: