@eladalon1983 We need: 1. To reference an element within the same process 2. This reference must not prevent GC of the element in that process 3. We need to pass this reference to another process _and back_ 4. We _don't_ need to dereference it in the other process Since we _won't_ dereference in other processes, I see nothing scary, unsafe, harder, permissive, or unclear. > A capturer could then convert the string back to a CropTarget and use it to shave off pixels. That's one level up, and seems irrelevant. I think the interesting part is _[how](https://w3c.github.io/mediacapture-region/#dom-browsercapturemediastreamtrack-cropto) "the user agent calculates the bounding box of the pixels belonging to the element, and crops the frame to the coordinates of this bounding box"_, which I would think has to happen in the capturee process where the element is, to track layout-movements of the element. Hence the _"and back"_. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-region/pull/24#issuecomment-1081142141 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-configReceived on Monday, 28 March 2022 21:05:02 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:56 UTC