Closed Bug 1631200 Opened 6 years ago Closed 6 years ago

Cursor is not shown for getDisplayMedia screen recordings

Categories

(Core :: WebRTC: Audio/Video, defect)

75 Branch
Unspecified
All
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: tobias_petry, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:75.0) Gecko/20100101 Firefox/75.0

Steps to reproduce:

Screen recordings with getDisplayMedia never show the cursor, this makes screen sharing very strange e.g. when you want to demonstrate something in a video conference.

Steps to reproduce:

Actual results:

Look at the screen recording below and search for your cursor, there is none

Expected results:

I expected the screen recording to show the cursor.

If you compare the behaviour of Firefox with all other browsers, you will notice that every other browser displays the cursor:

  • Safari: show cursor
  • Chrome: shows cursor
  • Opera: shows cursor
  • Edge (Chromium): shows cursor
  • Edge (EdgeHTML): shows cursor

Firefox should also show the cursor by default or at least implement MediaTrackConstraints.cursor to let the application determine the desired display state of the cursor.

I forgot to mention that the wrong behaviour only occurs on Windows and MacOS. Linux is showing the cursor except for some buggy versions (#1625694).

OS: Unspecified → Windows 7
OS: Windows 7 → All

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → WebRTC: Audio/Video
Product: Firefox → Core

Tobias, thanks for filing this bug. Can you try to reproduce this using Firefox Nightly? I tried to reproduce this using Nightly on Windows 10 and I could see my cursor.

Flags: needinfo?(tobias_petry)

On Firefox Nightly the cursor is displayed.

Flags: needinfo?(tobias_petry)

Ok, seeing as this is fixed in NIghtly, I am going to close this bug for now.

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.