- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Mon, 23 May 2022 07:04:49 +0000
- To: public-webrtc-logs@w3.org
> As the identifier will be attached to the Element, we can GC when the Element is GCed. Am I missing some complication? A CropTarget life can be much shorter than an Element. This is one thing that makes CropTarget appealing. With generated IDs, there is no other way than either having a revoke mechanism (like blob URLs, which is a very leaky mechanism) or expanding the lifetime of the ID to the Element itself. An Element might have a very long lifetime, especially with page cache, this is risky to rely on element destruction to do the clean-up. I believe CropTarget serialisation/postMessage should be sufficient for all current and future scenarios. We can certainly expand APIs to support CropTarget exchange through serialization/postMessage as needed. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/46#issuecomment-1134264037 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 23 May 2022 07:04:51 UTC