- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Feb 2025 17:02:55 +0000
- To: public-webrtc-logs@w3.org
A few thoughts: - This seems to be a valid interop issue. It apparently caused some issues for Safari in the past AIUI so we should fix it. The status quo is not good, web implementors should do their best to converge and help web developers. - Saying `we don't know whether that could break, so let's do nothing` is really disappointing and not healthy. I hear this argument much more often here than in other web areas. - I don't have a strong preference on which behavior to pick. I am ok trying to update WebKit behavior to what the WG deems appropriate. Let's first agree on trying to solve this issue or not. https://github.com/web-platform-tests/interop/issues/855 is a good example of trying to keep the web a sane place. Chrome and Safari will try to align with the spec. If it proves too difficult to align with the spec, we will likely discuss updating the spec (and Firefox). -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/1028#issuecomment-2685669226 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 26 February 2025 17:02:56 UTC