- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Tue, 04 Feb 2025 00:26:18 +0000
- To: public-webrtc-logs@w3.org
> I oppose notion that this is a feature of the video element. In https://github.com/w3c/mediacapture-surface-control/issues/69#issuecomment-2626774199 you agree there's a preview tile. Can we agree end-users will perceive this to be a feature of that tile? This tile can be a video element or a "preview-canvas" to use your suggested terminology. What's wrong with moving the API there? If it's important to you that we consider preview-canvas from the start, I'm open to doing that. ```js await previewVideoElement.forwardGestures(true, {overlay}}); await previewCanvas.forwardGestures(true, {overlay}}); ``` > We have received feedback to the contrary from Web developers we are in touch with. They have found the proposal to expose the API over the video element to be a regression in clarity and usability. Please provide verifiable evidence or let us examine that feedback directly. Otherwise this invocation of an external endorsement amounts to an appeal to unnamed authority, rather than engaging on first principles. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-surface-control/issues/45#issuecomment-2632483314 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 4 February 2025 00:26:19 UTC