- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Dec 2024 17:35:00 +0000
- To: public-webrtc-logs@w3.org
> That there are two implementations doesn't prevent changing the spec to improve it What is proposed is an entire rewriting the API/WebIDL, which means rewriting a large part of the spec. > The use case for managing the track on Window is all existing applications. It would help immensely if we have a solid proof that the new API is hard to use. So far, it does not seem to be the case. AIUI, the current API and the proposed API have the same feature set, so there should be no impact on end users. All we are debating is ease of use of the two APIs. We should compare this potential ease-of-use benefit with the known amount of work building the new proposal would require: 1. WebRTC WG discussions to reaching consensus on the new API design 2. Rewriting of the spec 3. Deprecation and removal of the current API (we surely do not want to have two APIs for the same job) 4. Reimplementations in all browsers. This is a big ask. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-transform/issues/113#issuecomment-2536653506 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 December 2024 17:35:02 UTC