Although this makes sense from a UX point of view, this sounds highly impractical to implement: oxide merely implements interfaces exposed by chromium for access to camera/microphone (actually not even for microphone, where it talks to pulseaudio directly, no oxide-specific code there). So it doesn’t actually catch events that request video/mic access.
Additionally, what if the two permissions are being asked with a 3 seconds delay (for any possible reason, including network lag)? We’d be back to the original situation. So where do we draw the line for this kind of situation? Let’s remember that this bug will affect users only the very first time they use the browser to access a webRTC service (or even possibly never if they used the browser to access microphone and camera separately in the past). It’s a perfectly valid bug, but its importance is probably low. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554149 Title: Asks for separate permission for microphone and camera To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/trust-store/+bug/1554149/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
