- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Tue, 24 May 2022 18:17:44 +0000
- To: public-webrtc-logs@w3.org
> What you appear to be saying is Chrome's implementation is authoritative and the spec is not and should be updated to match. Am I misreading that? You are indeed misreading it. > I oppose this view. We have that in common. > I think Chrome's implementation is buggy It will be "buggy" once shipped. Right now it's "incomplete", and that's not at all surprising, given how the spec continued to evolve past the point where the Origin Trial started - which is **par for the course** for Origin Trials. > But this is built into WebIDL bindings and happens synchronously. This issue is about whether generation of a valid target can fail. That the IDL bindings are going to make the implementation reject synchronously, is an implementation detail. The spec says that any Element should be accepted. But this is not necessarily going to happen with Chrome; not at any given point in time. I think it's very likely that Safari and Firefox will behave similarly. Specs are read by both implementers and developers. It's good if it alerts developers to risks such as partial implementations. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/48#issuecomment-1136286792 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 24 May 2022 18:17:45 UTC