- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Fri, 18 Oct 2024 18:03:28 +0000
- To: public-webrtc-logs@w3.org
I understand the urge to quickly go to API but I think it is a bit premature. There are some design decisions we should take consciously: - Allow/disallow web pages to select specific types of events and not others - Understand how web applications will know whether forwarding is working or not (my experience so far on Chrome Canari shows this is a real issue), and which events if we allow this flexibility. - Whether this is a capture controller thing or a MediaStreamTrack thing (difference in transferability) - Use permissions model or not (this is JS observable so we cannot have one UA do it and not another one) - Decide whether setting a specific zoom level should be part of the MVP (AFAIK, apps like browsers tend to provide easier access to increment zoom in/out) - Explore Command/+ and Command/- and pinch for zoom - Explore what could be translated to native surfaces and what could not be - Decide whether we should guarantee or not care about captured tab knowing it is captured I would suggest splitting these in sub issues that the WG will discuss in this repo. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share-extensions/issues/13#issuecomment-2422980720 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 18 October 2024 18:03:29 UTC