[mediacapture-screen-share] Define max frameRate constraint behavior when set to 0 (#253)

beaufortfrancois has just created a new issue for https://github.com/w3c/mediacapture-screen-share:

== Define max frameRate constraint behavior when set to 0 ==
I've noticed screen-capture web platform tests at https://github.com/web-platform-tests/wpt/blob/3728473b8ef5c7f382547d0809fe2d176c254f4c/screen-capture/getdisplaymedia.https.html#L174 say that `getDisplayMedia({video: {frameRate: {max: 0}}})` should fail with `OverconstrainedError`.

Looking at the [spec](https://w3c.github.io/mediacapture-screen-share/#dfn-framerate) though, it's not clear what the behavior should be.

![image](https://user-images.githubusercontent.com/634478/198532304-fec9b8e0-4c21-4939-8c68-d37ff9134b34.png)

One could argue that the browser could decide to make this call succeed but not send any video frames (Chrome does that), on the other hand the browser could also simply fail as not sending video frames could be seen as no-op (Firefox and Safari do that).

See https://wpt.fyi/results/screen-capture/getdisplaymedia.https.html?label=experimental&label=master&aligned
![image](https://user-images.githubusercontent.com/634478/198531878-f4226261-d9b6-401b-b11c-cbc8b5c830f2.png)
  

Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/253 using your GitHub account


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

Received on Friday, 28 October 2022 07:44:23 UTC