- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 Nov 2024 17:47:43 +0000
- To: public-webrtc-logs@w3.org
> ```js > // Implicitly affects an unknown number of capture sessions. > div.enableGestureForwarding = true; > ``` Sorry no, that's an incorrect understanding of what I'm proposing. To turn on forwarding would require ```js vid1.enableGestureForwarding = vid2.enableGestureForwarding = true; ``` With the div API, I'm trying to be generous and address the emoji/overlay use case. The idea would be a way to let the app mark which overlapping elements (in a div) if any should not block scroll inputs to a video element. But if it's confusing things let's keep things simple (your example did not include any overlays). > I also think it's poor choice of API to expose on HTMLElement or anything similarly high-level anything so capture-specific. I don't think this is good API design. I disagree obviously. There's plenty of precedent: - https://w3c.github.io/mediacapture-fromelement/#html-media-element-media-capture-extensions - https://w3c.github.io/mediacapture-output/#htmlmediaelement-extensions - https://w3c.github.io/remote-playback/#extensions-to-htmlmediaelement - https://w3c.github.io/encrypted-media/#htmlmediaelement-extensions -- 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-2460413508 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 17:47:44 UTC