Re: [mediacapture-surface-control] Is gesture forwarding tied to capture controller or to MediaStreamTrack or to DOM objects? (#45)

I agree with this use case. Thanks for the workaround idea. It's a clever reversal of typical manual forwarding one might expect a partially-interactive overlay to have to do using synthetic events: forwarding *back* to the overlay (backwarding?) to give the isTrusted property to the video element instead of the overlay.

The CSS folks I spoke with pushed back on a general `.overlay { wheel-events: none }` suggesting it may be a heavy lift. There's also https://github.com/w3c/mediacapture-surface-control/issues/54. They suggested something like `videoElement.forwardEvent(event)` but there's likely a good reason that doesn't already exist in the platform (once an event goes into JavaScript, the browser has limited visibility into exactly what the page might do with it).

If I were to rank these ideas I'd probably put the backwarding idea first.

But the simplest way might be to just declare that this API gets first dibs on input even when underneath an overlay.

How does Chrome's current API work here? Are trusted events emitted/can JS preventDefault() the behavior? Given the security principles we want for this API, it might actually be advantageous to bypass JS here.

> There is nothing in this shape to tie the video element to the captured surface, whereas the current API shape does.

That's a feature. The link is already implicitly through `video.srcObject`. Creating competing relationships is confusing.

> It'd be better to just s/HTMLElement/HTMLVideoElement in the original shape, then to make this change to HTMLVideoElement.forwardGestures().

Great, but that goes both ways: but if we can do `captureController.forwardWheel(HTMLVideoElement element)` then that seems indistinguishable from htmlVideoElement.forwardWheel()`, except for this (in my view undesirable) competing association.


-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-surface-control/issues/45#issuecomment-2587723308 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 13 January 2025 17:20:31 UTC