- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Jan 2022 10:19:03 +0000
- To: public-webrtc-logs@w3.org
I am not sure to follow, either BrowserCaptureMediaStreamTrack is for any tab capture or for self tab capture only. Can you clarify? My understanding is that this is the former. The spec is not clear here so it might be good to clarify the intent in the spec. I now see that https://github.com/w3c/mediacapture-region/issues/3 is sort of related. > * Expose `cropTo` more widely and expect applications to call it "optimistically" and be robust to failure. Applications will need to handle this anyway because RegionCapture may not match. > So arguably window/screen-cropping would be entirely separate APIs. Maybe, I could see cropTo used for the application/screen surface types (crop to focused window say). Yes, that case would probably best work if the track was listing its regions of capture ;-) cropTo could also take a union type if CropTarget is not good enough. Wild thought, there is nothing precluding other tracks to support cropping (say camera exposing specific regions and allowing to efficiently track-and-crop the corresponding region). -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/10#issuecomment-1022058758 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 26 January 2022 10:19:05 UTC