W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > January 2022

[mediacapture-region] Is BrowserCaptureMediaStreamTrack needed? (#10)

From: youennf via GitHub <sysbot+gh@w3.org>
Date: Tue, 25 Jan 2022 12:45:12 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-1113845656-1643114710-sysbot+gh@w3.org>
youennf has just created a new issue for https://github.com/w3c/mediacapture-region:

== Is BrowserCaptureMediaStreamTrack needed? ==
BrowserCaptureMediaStreamTrack is used for two purposes:
1. Make sure cloning does not clone the captured region
2. Restrict cropTo exposure to BrowserCaptureMediaStreamTrack
3. Make sure cloning produces a track that has a cropTo method.

1 seems unnecessary looking at the current clone algorithm.
3 is unnecessary, at least if we think 2 is not needed. Probably it is unnecessary given that CanvasCaptureMediaStreamTrack clone is a CanvasCaptureMediaStreamTrack and does not expose a dedicated clone method. 

The question is then whether it is better to expose cropTo at MediaStreamTrack or at BrowserCaptureMediaStreamTrack level.
I am not sure BrowserCaptureMediaStreamTrack is worth it for the sole purpose of exposing cropTo, we are anyway exposing https://w3c.github.io/mediacapture-screen-share/#displaycapturesurfacetype.

Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/10 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 25 January 2022 12:45:13 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:55 UTC