- From: Tove Petersson via GitHub <sysbot+gh@w3.org>
- Date: Mon, 02 Dec 2024 11:49:23 +0000
- To: public-webrtc-logs@w3.org
> Updating the settings before the callback makes sense to me, and the only way currently is for `configurationchange` to fire first. If a callback is really desired, a compromise would be the following: > > * enqueue a task on each track to fire `configurationchange` on each track task queue with MediaStreamTrack task source > * enqueue a task to execute the callback on capture controller task queue with MediaStreamTrack task source My concern with this ordering is how applications know that the user is switching surfaces at the time of the `configurationchange` event. Do you have a mechanism in mind that you think we can agree on? Otherwise I think we should reverse the order of these tasks. -- GitHub Notification of comment by tovepet Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share-extensions/issues/15#issuecomment-2511321914 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 2 December 2024 11:49:24 UTC