- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Tue, 01 Feb 2022 09:47:35 +0000
- To: public-webrtc-logs@w3.org
I agree that it's ready for PR, if the PR says that the user agent MAY reject/ignore any type it deems risky. (I have no strong preference between reject and ignore.) As mentioned, Chrome currently defaults to offering screens first, and this is something that I would very much like to change. However, changing established patterns has the effect of ruffling many feathers, and applications are not less upset when we tell them that the new behavior is "WAI, see spec." The reality is that Chrome rolls back changes that prove overly unpopular. To cite one recent example, colleagues of mine have run into such [issues](https://bugs.chromium.org/p/chromium/issues/detail?id=1286760) when aligning Chrome implementation with the spec with respect to making `getUserMedia` wait for focus, and this ended up being rolled back. Specs are much more useful when they're in-line with actual implementations. We don't want browsers to default to screens-first when no-ideal-screen-specified, but Chrome might be pushed to do so if the Working Group insists on a puritan stance that mandates "MUST reject" instead of "MAY reject" for `"monitor"`. For the sake of the Web, let's allow each other room to maneuver. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/184#issuecomment-1026652675 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 09:47:36 UTC