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

Re: [mediacapture-region] Make CropTarget serializable (#24)

From: Elad Alon via GitHub <sysbot+gh@w3.org>
Date: Tue, 29 Mar 2022 08:54:24 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1081607565-1648544062-sysbot+gh@w3.org>
> We need to pass this reference to another process and back

Citation needed for "and back" - see below.

> which I would think has to happen in the capturee process where the element is

The process where the element originates does not need to be consulted again. That might be a valid implementation, but it's not a necessary implementation. Allow me to tell you about Chrome's implementation. Chrome "tags" the Element in the rendering pipeline as soon as `produceCropTarget()` is called. This tagging travels along to the GPU process, which collates data from the many processes associated with the different frames. The process where the Element lives never finds out that it's being captured, let alone that an active capture is being cropped to an Element in said process.

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

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 29 March 2022 08:54:25 UTC

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