W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > April 2019

Re: [mediacapture-screen-share] Issue 38 - Cursor constraint (#58)

From: guest271314 via GitHub <sysbot+gh@w3.org>
Date: Tue, 02 Apr 2019 07:27:08 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-478877587-1554190026-sysbot+gh@w3.org>
@juberti FYI Tried `.getDisplayMedia({video: {cursor: "never"}})`, `videoTrack.applyConstraints({cursor: "never"})` and `videoTrack.cursor = "never"` at Chromium 72. Neither removed the cursor entirely from the captured media stream

![cursor](https://user-images.githubusercontent.com/4174848/55383818-9cd08c80-5518-11e9-9177-a0306b40c07c.png)

![cursor_1](https://user-images.githubusercontent.com/4174848/55383826-a659f480-5518-11e9-9c66-9f541cb044d6.png)


After setting the constraints `videoTrack.getSettings()`

https://developer.mozilla.org/en-US/docs/Web/API/MediaStreamTrack/getConstraints#Return_value

> To get the currently active settings for all constrainable properties, you should instead call `getSettings()`.

the resulting object still had `cursor` set to `"always"`

```
{aspectRatio: <value>
cursor: "always" // after applying constraints to the (video) `MediaStreamTrack`
deviceId: <value>
displaySurface: <value>
frameRate: <value>
height: <value>
logicalSurface: <value>
resizeMode: <value>
videoKind: <value>
width: <value>}
```

Outside of using `.pointerLock()` CSS `element {cursor:none}` was the code that resulted in the cursor not being rendered as part of the media stream.

The screen-capture directory at wpt there does not appear to include a test for cursor. 



-- 
GitHub Notification of comment by guest271314
Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/pull/58#issuecomment-478877587 using your GitHub account
Received on Tuesday, 2 April 2019 07:27:09 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 4 June 2019 15:32:56 UTC