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

A few points were identified during yesterday's informal meeting:

There are two underlying models behind these approaches.
- Capture controller-based API model: the overlay element defines the surface that can receive the events. UA is responsible to reduce the events to the ones in the renderer element bounding box.
- Renderer-based API model: the renderer element is the surface that receives the events. UA is responsible for making sure that the registered overlay elements are not catching these events.

Following from this:
- Capture controller-based API allows an arbitrary large surface to get the events that may be used for scrolling
- Renderer-based API limits the event-receiving surface to itself
- There is consensus that only events in the renderer-based surface should be used for scrolling.

It would be good to study:
- Which underlying model is simpler to understand from web developers.
- Which underlying model matches better existing UA rendering/eventing management model.
- Which underlying model is easier to implement (may be same point as above).
- How existing events like touch events are managed/propagated (could help above point).

Exploring the case of a transferred MediaStreamTrack (or transferred VideoFrames) would be useful:
- The rendering elements, the capturing document and the captured surface could all live in separate environments.
- This use case requires CaptureController to be transferable with the CaptureController based API. It would work directly with the rendering based API.
- If the rendering element is in a different page than the capturing document, who should own the scrolling permission? the permission indicators?

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


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

Received on Wednesday, 19 March 2025 09:32:30 UTC