- From: handellm via GitHub <noreply@w3.org>
- Date: Thu, 11 Sep 2025 08:56:18 +0000
- To: public-webrtc-logs@w3.org
Hi @jan-ivar, when adding HEVC support we had some internal discussion on wether we should allow wildcardish operation and the conclusion at the time was to not allow it. We support allowing user agents that implement the wildcard strategy to fire an event asynchronously, but we want to allow Chrome to continue to do what it is doing (i.e. throw exception at construction or have isTypeSupported return false for codec.* types) for backwards-compat reason. We think it would be more ideal to feature freeze rather than change. -- GitHub Notification of comment by handellm Please view or discuss this issue at https://github.com/w3c/mediacapture-record/pull/226#issuecomment-3279289537 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 11 September 2025 08:56:19 UTC