- From: Jan-Ivar Bruaroey via GitHub <noreply@w3.org>
- Date: Thu, 11 Sep 2025 18:37:21 +0000
- To: public-webrtc-logs@w3.org
> 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. I plan to update the PR based on https://github.com/w3c/mediacapture-record/pull/226#issuecomment-3140287250 to include `hev1`, `hvc1`, `avc3`, `avc1` to the list, making them "old codecs", effectively freezing (making throwing in the constructor spec for them). The compromise is to limit detection to wildcards, to reduce the fingerprinting surface. In my experience, web compat issues usually comes in the form of web devs forgetting to test their input with Safari or Firefox, not Chrome. So Chrome having a stricter test on input than spec (for a subset of its codecs) shouldn't break any web devs here. It seems Chrome should be able to unify detection of its latest codecs with its other codecs here without breaking anyone. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-record/pull/226#issuecomment-3282199722 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 18:37:22 UTC