- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Fri, 09 Feb 2024 13:32:58 +0000
- To: public-webrtc-logs@w3.org
> But I am willing to lean in and actually claim it. Yes, developers need the early-decision, because cross-surface-type(!) source-injection is a footgun. Consider the code in this fiddle: https://jsfiddle.net/eladalon/Ly8a3wcs/ I can now substantiate this claim in a more persuasive manner. Try out [captured-surface-control.glitch.me](https://captured-surface-control.glitch.me) using Chrome Canary. Observe: 1. If you choose a window, the application stops the capture and bids you try again. 2. If you choose a tab, the application "activates" and there is a built-in assumption that you keep on sharing a window. Applications built before cross-surface-type source-switching was possible had no reason to expect that `getSettings().displaySurface` might be mutable, and they are not robust to these changes. -- Note: Of course Captured Surface Control is not a standard API. Assume for the sake of argument that it never will be. The whole point here is to show that in the future, we could credibly add APIs that would work for one surface types but not for others, and that unexpected switching would break apps. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/255#issuecomment-1935936259 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 9 February 2024 13:33:01 UTC