- From: Tove Petersson via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 Nov 2023 10:43:05 +0000
- To: public-webrtc-logs@w3.org
There are limitations on which types of surface switching a user agent can perform without the help from the application, e.g., adding audio requires the application to act on the change for it to take effect. Since the user agent is expecting the application to perform an action in this case, the API should be designed to reflect that. By giving the application a new MediaStream that it needs to use, there is less risk of an application writer, e.g., forgetting to check if an audio track has been added. It is also important for the user agent to know in advance if the application intends to act on a surface change so that it can offer the appropriate options, e.g., it should not give the option to add audio if the application is going to ignore that. Setting a callback, can provide this information to the user agent. I think there might be a dividing line in this discussion between if we primarily look at this functionality as a way for applications to perform the required setup for when the mediastream changes in a material way, or if it is about getting notified about a change having occurred. Perhaps we want to have both a callback for the former purpose and an event for the latter? -- GitHub Notification of comment by tovepet Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/255#issuecomment-1812229590 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 15 November 2023 10:43:07 UTC