W3C home > Mailing lists > Public > public-webrtc@w3.org > August 2020

[mediacapture-image] Stop referring `advanced` constraints (#252)

From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
Date: Mon, 24 Aug 2020 17:54:07 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-684855780-1598291646-sysbot+gh@w3.org>
jan-ivar has just created a new issue for https://github.com/w3c/mediacapture-image:

== Stop referring `advanced` constraints ==
This spec refers to the overly complex and outdated [advanced](https://w3c.github.io/mediacapture-main/getusermedia.html#dom-constraints-advanced) constraints syntax in:
1. [examples](https://w3c.github.io/mediacapture-image/#examples)
2. In issues like https://github.com/w3c/mediacapture-image/issues/243#issuecomment-674090590, where apparently one browser infers new meaning from their presence

The former is unnecessary, and the latter is a non-standard.

The differences between the older `advanced` constraints and the modern `ideal` constraints are [minimal](https://w3c.github.io/mediacapture-main/getusermedia.html#example-3) and best forgotten. TL;DR: they allowed for non-linear fallbacks between `width` x `height` x `frameRate` combos when `resizeMode` is `none`. They're largely redundant elsewhere, since most other constrainable capabilities are orthogonal to each other.

It's therefore best to not mention them, to discourage use. Maybe one day we'll be able to remove them from the platform.

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

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 24 August 2020 17:54:09 UTC

This archive was generated by hypermail 2.4.0 : Monday, 24 August 2020 17:54:11 UTC