- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 Nov 2024 15:32:07 +0000
- To: public-webrtc-logs@w3.org
> div.setGestureForwarding() ...
I agree promise can be discussed separately.
> 1. It assumes a single video element with a single capture. (If not, which one is being forwarded?)
No, the idea is the developer declares where they expect forwarding, and the user agent makes it happen where it can happen:
- videoElement.setGestureForwarding() and canvas.setGestureForwarding() forward to what they're playing/rendering
- div.setGestureForwarding() would pass-through to videoElements or canvases underneath the div, without extending hit areas.
This would be a declarative API — putting the user agent in charge of where forwarding happens instead of the app — so reusing the same API name seemed simple, but if it's confusing I'm open to other ideas. Other ways to solve pass-through might be with CSS, something similar to `.overlay { pointer-events: none; }` maybe? The problem space here seems a bit outside WebRTC, so we might want to get input from DOM folks.
--
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-2460082800 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 6 November 2024 15:32:08 UTC