- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Fri, 04 Aug 2017 17:25:15 +0000
- To: public-media-capture-logs@w3.org
When it comes to **video resolution and frame-rate**, I suspect some may have reservations about getting non-native modes, given the constraints-language's focus on device discovery. cc @fluffy That said, as Firefox's implementation shows in https://github.com/w3c/mediacapture-main/issues/465#issuecomment-320261591 there are side-effects from having no virtualization at all: Changes in one tab, end up observably affecting another, live. Not great. As a browser, we're keen to abstract away effects of other domains whenever possible, for privacy reasons as well as more deterministic behavior. So we're looking at maybe doing some rescaling, at least to address our concurrent access situation. But we're also concerned by an apparent rise in mininum supported resolution in at least some newer cameras (new MBP internal cams seem to offer only 640x480 and 1280x720). So we're contemplating filling in low-res gaps with "divide-by-2" virtual modes. Group thoughts? @guidou My tests with Canary and chrome://flags/#enable-experimental-web-platform-features today seem to produce native modes when available (in a single tab at least), which is terrific! It appears to fall back to rescaling, only failing with `OverConstraintedError` if I go above camera max. Does that match your expectation? -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/466#issuecomment-320306255 using your GitHub account
Received on Friday, 4 August 2017 17:25:17 UTC