- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Mon, 20 Nov 2023 14:05:17 +0000
- To: public-webrtc-logs@w3.org
Thanks, @youennf, for presenting use cases. I note that these examples don’t demonstrate genuine need by the application for source-injection; these are hypothetical examples about why some applications *might* use it. These applications would be able to accomplish the same functionality with the new model with no great difficulty, and I’d argue that it would even produce simpler and more straightforward code. (Conditionally suppressing defaults is not as common a pattern as “old thing replaced by new thing - plug it into srcObjects and peer-connections where it's still useful.”) If others are not worried about the footguns of interaction between different event-handlers, I am willing to let that be and go with events, provided that: * The decision to source-inject is finalized when calling gDM. * All handlers get references to the same new stream and track(s), rather than to clones or independent tracks. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/255#issuecomment-1819124904 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 20 November 2023 14:05:19 UTC