Re: [mediacapture-region] Need for a predictable error type for unimplemented Element subtypes (#55)

> > Implementers are motivated to implement missing functionality, independently of compliance.
> 
> [Here](https://crbug.com/1328836#c1) you seem motivated by compliance.

That's a non sequitur. Of course Chrome cares about compliance, but how is that relevant? Would Chrome now ship null-functioning APIs and declare success? Has Chrome funded this effort of standardization and implementation of Region Capture as a strange joke? What do you mean to say here?

I also ask you to examine with your chair's hat on, whether your comment here falls within the guidelines of this WG's discourse.

> > Where is the bar?
>
> ...

Thanks for clarifying your positions here, @jan-ivar and @youennf. I disagree with your bar, but now I know where it is.


-- 
GitHub Notification of comment by eladalon1983
Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/55#issuecomment-1236718784 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 5 September 2022 08:53:02 UTC