- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 May 2022 06:26:13 +0000
- To: public-webrtc-logs@w3.org
Here are some pros/cons for IDs. Pros: - No new API needed for some scenarios: just send the element ID (or capturer might know the ID in advance). Cons: - To identify the remote document, relying on WindowProxy is good, relying on MessagePort is brittle/subject to race conditions: it can be transferred or closed. - The general case is not supported. Things to further evaluate - Do we need to support the general case? If so a new API might be needed, either now or as a folllow-up. - An element ID can change. Either capture should follow ID changes or we are ok living with potential races and inconsistencies (cropTo with the same ID on two cloned tracks leading to different frames). - Security implications of allowing an application that captures an iframe to crop without the iframe help. It is unclear to me what the potential issues are. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/11#issuecomment-1123235239 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 May 2022 06:26:14 UTC