- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Mon, 07 Aug 2017 02:00:50 +0000
- To: public-media-capture-logs@w3.org
> If that was the intention was to select only native modes, it did not make it into the spec. @guidou I notice you didn't dispute the shortcomings I mentioned. Both Firefox and Edge let users discover best-match device modes using the [above](https://github.com/w3c/mediacapture-main/issues/466#issuecomment-320485062) examples with quite a bit of precision, with `advanced` lending even more precision. Those browsers do it without exposing an exhaustive list of device capabilities to the JS. This is quite an accomplishment that would not have been possible without the full intent of the spec behind it. It's why constraints is a bit of a mini-language. This is not possible in Chrome. That seems like a shortcoming. > The spec does not make any reference to native vs. non-native video modes. Right, no mention of downscaling, except to "ensure that all tracks have appropriate media", this issue. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/466#issuecomment-320550696 using your GitHub account
Received on Monday, 7 August 2017 02:00:50 UTC