W3C home > Mailing lists > Public > public-media-capture-logs@w3.org > May 2017

[mediacapture-main] Mark 'advanced' constraints as legacy?

From: jan-ivar via GitHub <sysbot+gh@w3.org>
Date: Wed, 17 May 2017 19:50:26 +0000
To: public-media-capture-logs@w3.org
Message-ID: <issues.opened-229467789-1495050625-sysbot+gh@w3.org>
jan-ivar has just created a new issue for https://github.com/w3c/mediacapture-main:

== Mark 'advanced' constraints as legacy? ==
Can we mark `advanced` constraints as legacy? Doing so might help explain the redundancy in the spec, and point people toward the semantically simpler syntax the WG arrived at.

We're starting to see people using advanced constraints for things that are not advanced at all, [even in spec examples](https://github.com/w3c/mediacapture-image/pull/175#discussion_r116855344). I wanted to discourage it, but found no language to lean on. Can we add some?

Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/455 using your GitHub account
Received on Wednesday, 17 May 2017 19:50:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:27:32 UTC