- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Thu, 07 Nov 2024 14:51:21 +0000
- To: public-webrtc-logs@w3.org
> 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). It is only confusing because a suboptimal API is proposed. But with the proposal of `CaptureController.forwardWheelFrom(element)`, it is neither confusing, **nor do we need to compromise on functionality**. So I don't see a reason to change away from that proposed API. > I disagree obviously. There's plenty of precedent: All of these precedents are on `HTMLMediaElement`, not on `HTMLElement`. They are somewhat natural for a media-element, but would be quite confusing for a non-media-element. > In contrast, putting the API on the controller lets apps express things we don't want to support, like: It's a small price to pay in order to allow forwarding from the application's choice of overlaid surface. It's a common cost for flexibility. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share-extensions/issues/20#issuecomment-2462432724 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 7 November 2024 14:51:22 UTC