You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CaptureController lives where capture was initiated.
MediaStreamTrack on the other hand can be transferred and lives where it is being rendered.
This makes it potentially possible for CaptureController and the getDisplayMedia track to live in different contexts.
Given gesture forwarding is tied to the track's preview, it seems it is more tied to MediaStreamTrack/HTMLVideoElement than CaptureController.
The question is then whether API should be tied to CaptureController or to HTML elements/MediaStreamTrack.
I would then to favour the latter.