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

Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)

From: Elad Alon via GitHub <sysbot+gh@w3.org>
Date: Mon, 21 Mar 2022 15:59:46 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1074078015-1647878385-sysbot+gh@w3.org>
> what happens in case the element goes transferred to another document

I've had the same concern. I lost that concern when I learned that Elements are not transferable. (But do correct me if I am wrong.)

> which then gets destroyed

It is generally possible for a CropTarget to outlive its Element, and that's OK. The document discusses what happens then. The summary is:
* If cropped to a target that is in the DOM, has >0 pixels, etc., frames are produced.
* Otherwise, no further frames are produced. The track is effectively "muted" (but without the muting - as per our earlier agreement).
* Elements can be garbaged collected even! That's not special. It falls into the category set by the previous bullet-point.
* It's always possible to get a track "unstuck" by calling cropTo again, either to uncrop it or to re-crop it to a new target.

GitHub Notification of comment by eladalon1983
Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/17#issuecomment-1074078015 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 21 March 2022 15:59:48 UTC

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