screen sharing wayland requires multiple permission dialogs
Categories
(Core :: WebRTC: Audio/Video, defect, P3)
Tracking
()
People
(Reporter: mattias.eriksson, Unassigned)
References
(Blocks 1 open bug)
Details
User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:76.0) Gecko/20100101 Firefox/76.0
Steps to reproduce:
Using Fedora 32 and Firefox 76.0.1 from fedora repository, I started a meeting on http://meet.jit.si and shared my screen.
Actual results:
I got a permission request asking me to select a window or screen, I then select Entire Screen. I'm then presented with a xda-desktop-portal screen selector, where I select one of my two screens and click "Share". A preview of that screen is now showed in the firefox permission dialog and I click "Allow".
I'm now presented with a second xda-desktop-portal screen selector dialog, where I have to select the same screen again and click "Share" and then the screen is shared.
Expected results:
After I click "Allow" on the firefox permission dialog, the screen should be shared and no second xda-desktop-portal screen selector should be needed.
Ok, I realize the description above is how screen sharing at http://meet.google.com behaves, for jitsi I'm actually presented with a third xda-desktop-portal screen permission (while the screen actually seems to be shared in the background).
|
||
Comment 2•4 years ago
|
||
Because we show a preview, there are two separate requests to share the screen, one made from the browser's parent content for the UI, and one made from the content context, for the page itself. That would explain two of the permission requests.
Right now, we don't build Firefox with Wayland screensharing support, we've landed patches contributed by Fedora to allow for it, but it isn't enabled in our builds. It is a build system limitation (see Bug 1430775). For now, this isn't something we'll work on. I'd suggest filing a bug with Fedora, as they are probably in a better position to fix this.
I'll leave the bug open, as this is something we'd want to investigate once the build system stuff is cleared up.
See also: bug 1685694.
Description
•