- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Tue, 05 Nov 2024 22:25:29 +0000
- To: public-webrtc-logs@w3.org
My mental model is this is about enabling user controls, not app controls. This suggests it might be logical to put the API on the DOM objects the user interacts with. This is why I find @youennf's API in https://github.com/w3c/mediacapture-screen-share-extensions/issues/13#issuecomment-2427791931 appealing. E.g.: ```js videoElement.enableGestureForwarding = true; div.enableGestureForwarding = true; // if on top canvas.enableGestureForwarding = true; // recently drawn to with video ``` MediaStreamTracks can be cloned and transferred to workers, where gesture forwarding doesn't make sense, so I don't think that's the right place. OTOH, CaptureController.forwardWheel(x) only supports one x, and x = null is how to stop fowarding (a bit surprising that). It may be uncommon to have two preview elements, but if a website wants it, as a user I'd expect to be able to scroll both. This to me suggests an element API. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share-extensions/issues/20#issuecomment-2458263750 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 5 November 2024 22:25:30 UTC