Bug 253024 – getDisplayMedia prompt failure leads to getDisplayMedia prompt and media capture failures on reload

• Status: NEW
• Component: WebRTC

[Steve Mieskoski]

Created attachment 465204 [details]
Console log after screen share permission prompt would no longer display on getDisplayMedia calls

Occasionally when calling 'getDisplayMedia' the permission prompt will fail to display.  Safari will have the permissions for 'screen sharing' set to 'ask' but the prompt fails to display.  More significantly, when the page is reloaded the permission prompts for 'getUserMedia' will also fail and the page is unable to access either the microphone or camera regardless of what the user sets the permissions to via the settings menu.  I was able to force this behavior after several minutes of calling 'getDisplayMedia', canceling the 'screen share', and then calling 'getDisplayMedia' again (also muting/removing the audio or video track during this forced sequence of steps as well). Our QA people have reported this occurring in with some frequency during their normal testing work.  

I used meet.jit.si (with two users [one on each of two machines]) as a public setup to forcefully reproduce this issue. 

Safari Version 16.2 (18614.3.7.1.5)

[Radar WebKit Bug Importer]

<rdar://problem/106318915>

We're observing this issue on the current setups:
MacOS: 13.2.1 Ventura
Safari 16.3, 16.4
It is reproducible every time.

Safari has been given Screen Recording permissions in the System settings.

When we try to share the screen, it fails with this error in the console:
"A MediaStreamTrack ended due to a capture failure"

I tried experimenting with the video constraints while calling getDisplayMedia(). When sending a basic object in as video constraints like below, the screen sharing works perfectly fine.
{
    aspectRatio: 1.777,
    frameRate: 10,
}


However, if we send in video constraints like these, we observe the problem.
{
    "cursor": "always",
    "aspectRatio": 1.77,
    "frameRate": 10,
    "height": 1080,
    "width": 1920
}

{
    cursor: "always",
    frameRate: 10,
    height: 1080,
    idealHeight: 1080,
    idealWidth: 1920,
    maxHeight: 1080,
    maxWidth: 1920,
    width: 1920
}

Please disregard my previous comment. I believe the issue I'm reporting is different from the issue reported in this bug.