- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Mon, 21 Oct 2024 21:42:32 +0000
- To: public-webrtc-logs@w3.org
> Based on this, I would look at an API along those lines:
> ```webidl
> partial interface HTMLVideoElement {
> attribute boolean enableGestureForwarding;
> };
> ```
> ... This ... unties the API from permissions.
I favor this API. Reusing the playback coupling through `video.srcObject` is elegant, intuitive, and foolproof. We should consider letting UAs limit forwarding to when the capture is visibly playing, so users see what they're interacting with.
> ```js
> controller.forwardGestures(e1, {wheel: true});
> ```
I do not favor this API. It allows mistakes like forwarding to a capture other than the one playing. Also, dictionary default rules mean `controller.forwardGestures(e1)` turns forwarding *off* which seems surprising and unintuitive.
I'm also not convinced apps need to cherrypick behaviors in the first version. I'm not convinced about divs.
> Chrome does not plan to provide zoom through its UX. Does Firefox? Does Safari?
Firefox might put zoom controls in the video element (next to its PiP button).
--
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share-extensions/issues/13#issuecomment-2427791931 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 21 October 2024 21:42:32 UTC