- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Tue, 01 Feb 2022 12:31:24 +0000
- To: public-webrtc-logs@w3.org
> > if the Working Group insists on a puritan stance > > I don't think this comment helps moving the discussion forward. I have consulted Merriam Webster in order to double-check my vocabulary, and as far as I can tell, I got it right: ``` Definition of puritan (Entry 1 of 2) ... : one who practices or preaches a more rigorous or professedly purer moral code than that which prevails ``` I think my comment is polite and relevant. It discusses an important principle - the trade-off between what the Working Group wants (crisp-clear spec that mandates user agents MUST provide the best thing for the user, with no regard for the constraints of historical decisions), and what the Working Group can reasonably expect to have (an ever-shifting compromise between multiple entities with various constraints). > We already discussed in a past meeting the possibility for Chrome to do this change without waiting for either this PR or any additional spec change Could you point to precedents where Apple or Mozilla have knowingly accepted spec-changes that would put them in violation of the spec, where a minor change would have eliminated this problem? (Clarification - this refers to `MUST reject 'monitor'` vs. `MAY reject 'monitor'`. When it comes to constraints, I am not a fan either, but I leave this discussion in your most capable hands.) -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/184#issuecomment-1026793679 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 1 February 2022 12:31:26 UTC