Bug 269961 – Screen share / getDisplayMedia() buggy behavior and usability issues

• Status: RESOLVED
• Resolution: FIXED
• Component: WebRTC

Created attachment 470023 [details]
Alignment and pillarboxing issue when screen sharing in Safari

Me and several of our users constantly encounter issues when sharing screens on macOS Safari with getDisplayMedia()

Issue 1: Weird pillar boxing behavior. When sharing a an application/window, the content will be left aligned and have a weird black rectangle/pillarbox effect on the right side. See attached photo . This can be reproduced in multiple apps like Google Meet, webinar software, etc... For example, launch a quick Google Meeting and try to share a window that isn't 16:9 and you'll see the weird pillarboxing behavior.

Issue 2: Sometimes when attempting to screen share, if you select that you want to share a window, then attempt to select the window/application you want by navigating to the desired window/app, even when you click on the window nothing will happen. The screen share will just be entirely blank. Sometimes I will need to literally close out of the tab entirely and then return in order to get screensharing to work again at all.

Issue 3: In general I really think the screen share design is not intuitive compared to other browsers. Other browsers when calling getDisplayMedia() present a little list/popup with the option to select your various apps/windows, your entire screen, and various browser tabs. Simply select what you want from the list/popup and click share and then you're good to go. Safari on the other hand has a relatively convoluted process where you need to navigate to the macOS application/window and then click on said application/window, and then return back to Safari. Personally I think it harms the user's context and I wish Safari would follow other the browsers lead on this aspect.

[Radar WebKit Bug Importer]

<rdar://problem/123492622>

[youenn fablet]

Can you tell use which macOS version you are using?

Sonoma 14.3.1 but this issue has been around since those new screen/video features in macOS came out.

[youenn fablet]

Let's use this bug to focus on issue 1.
For issue 2, I filed https://bugs.webkit.org/show_bug.cgi?id=270458.

[youenn fablet]

Pull request: https://github.com/WebKit/WebKit/pull/25490

[youenn fablet]

Following black frames fix for window in https://bugs.webkit.org/show_bug.cgi?id=270568.

[EWS]

Committed 275736@main (ad55417ef5c2): <https://commits.webkit.org/275736@main>

Reviewed commits have been landed. Closing PR #25490 and removing active labels.

[EWS]

Committed 275742@main (8bdf93874c28): <https://commits.webkit.org/275742@main>

Reviewed commits have been landed. Closing PR #25537 and removing active labels.

[youenn fablet]

Re-opening for pull request https://github.com/WebKit/WebKit/pull/25577

[EWS]

Committed 275789@main (c557c381299f): <https://commits.webkit.org/275789@main>

Reviewed commits have been landed. Closing PR #25577 and removing active labels.

[youenn fablet]

*** Bug 270628 has been marked as a duplicate of this bug. ***