New issue
Advanced search Search tips

Issue 889516 link

Starred by 1 user

Issue metadata

Status: Unconfirmed
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Mouse position inaccurate for desktopCapture MediaStream

Reported by pdragu...@gmail.com, Sep 26

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36

Steps to reproduce the problem:
Steps to reproduce the problem:
1. Get a reference to a desktopCapture MediaStream via the chrome.desktopCapture API.
2. Get a reference to a microphone MediaStream via the window.navigator.webkitGetUserMedia API.
3. Add the audio track from the microphone MediaStream to the desktopCapture MediaStream.
4. Record the resultant stream via the MediaRecorder API.

What is the expected behavior?
The mouse is shown in the correct place when the recording is finished

What went wrong?
The cursor position in the video ends up being more than 25% of the screen dimensions off from where the user is actually pointing to. Here is an example video: https://www.useloom.com/share/f2f863ec50b8429d84ead1331e846400

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 68  Channel: stable
OS Version: 10
Flash Version:
 
Labels: Needs-Milestone
Components: -Blink>MediaStream Blink>GetUserMedia>Desktop
Cc: braveyao@chromium.org
Interesting. Can you see same problem when you do screen sharing in a Hangout meeting? Or this only happens at doing MediaRecorder?

Need more facts:
- Does this only happen on Windows 10? How about MacOSX/Linux?
- What's your test setting, a Win10 machine with one monitor?
- audio track should has nothing to do with this issue. Just to make things simpler, will this happen when you only record desktop stream?
- Do you have any test page that I can try to reproduce it?
Labels: Needs-Feedback Triaged-ET
Adding Needs-Feedback label as per comment #4.

pdragunas@ Request you to check and update the thread as per comment #4, which will help in further triaging of the issue.

Thanks..

Sign in to add a comment