Open Bug 956854 Opened 8 years ago Updated 5 months ago
Implement front end Permission UI for Web
User Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36 Steps to reproduce: I compile seamonkey 2.23 under mageia3 linux with WebRTC and gstreamer. I load the site contains WebRTC application for testing it. Actual results: WebRTC core initialized, but not shown dialog to allow/disallow/select microphone and webcam, and no access is granted. I tried to set media.navigator.permission.disabled;true , the microphone and webcam started working normally, but it is does not allow to control access. Expected results: Normal operation like as firefox: after loading the site shown dialog to access to the microphone and webcam, allowing access and use the application on the site.
iceape-2.22 has similar bug.
This is a known issue. We don't have any support for webRTC at the moment.
Status: UNCONFIRMED → NEW
Component: UI Design → General
Ever confirmed: true
I can use webRTC in seamonkey, it is really working, but webcam and microphone is always enabled or always disabled by default. about:config media.navigator.permission.disabled;true
No other way to enable access to microphone and webcam. It is uncomfortable and possible insecure.
(In reply to sysop5410 from comment #3) > I can use webRTC in seamonkey, it is really working, but webcam and > microphone is always enabled or always disabled by default. I see. I've changed the Summary for this bug slightly
Component: General → UI Design
OS: Linux → All
Hardware: x86 → All
Summary: WebRTC media permission UI is not shown → Implement front end Permission UI for WebRTC
As long as SeaMonkey doesn't have a WebRTC permissions UI, would it make sense to include a setting or toolbar button to toggle media.navigator.permission.disabled? On one hand, this would make SeaMonkey compatible with WebRTC applications (mostly); on the other hand, leaving media.navigator.permission.disabled=true after you're done with it is not a good idea and we might not want users to do that by accident.
I've made an extension that adds a toolbar button to toggle the setting on and off, if that helps anyone. https://github.com/IsaacSchemm/webrtc-permissions-ui-toggle
Once this is implemented, there should also be a way to install and/or disable OpenH264.
You need to log in before you can comment on or make changes to this bug.