@youennf, please note that the current version of the proposal is intentionally restricted to cases of **self-capture**, meaning the capturer **is** the capturee; or, at least, both are documents in the same browsing context (i.e. tab). As such, Capture Handle is **not** currently necessary. The various documents in the browsing context are already tightly integrated and in communication with each other. The only missing functionality - verifying self-capturedness - is possible by optimistically calling `cropTo` and seeing an exception raised if the capture is not self-capture. If you mean to suggest that we add an interface associated with the **capture session itself**, `NAME_TBD`, and expose various capabilities on it, then I would say I don't think that's ideal, as we might wish to clone a track and crop the clones differently. (Currently [challenging](https://github.com/eladalon1983/region-capture/issues/2#issuecomment-990308476), but ultimately possible and useful.) -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/195#issuecomment-993817598 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-configReceived on Tuesday, 14 December 2021 17:35:42 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:55 UTC