- From: guidou via GitHub <sysbot+gh@w3.org>
- Date: Sun, 06 Aug 2017 10:48:05 +0000
- To: public-media-capture-logs@w3.org
@jan-ivar If that was the intention was to select only native modes, it did not make it into the spec. The spec does not make any reference to native vs. non-native video modes. It only talks about settings dictionaries, and Chrome runs the SelectSettings algorithm with both native and non-native dictionaries as part of the set of valid dictionaries. If, after discarding all dictionaries that don´t satisfy the basic/advanced constraint sets, a candidate that equals ideal is present, it is selected because it will have the best fitness, as indicated by the spec. This is the correct result in Chrome with the spec as written. With regards to the advanced example, the spec says that naked values in advanced sets mean exact, so after analyzing the first constraint set (exact 180), no candidates that satisfy exact 200 remain and the second set is ignored. Thus the result is always going to be dictionaries with height = 180. Advanced sets that contradict previous advanced sets are often not useful because in most cases they will be ignored. I see nothing incorrect in that. -- GitHub Notification of comment by guidou Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/466#issuecomment-320499333 using your GitHub account
Received on Sunday, 6 August 2017 10:48:07 UTC