- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Thu, 23 Jun 2016 05:14:39 +0000
- To: public-media-capture-logs@w3.org
Jan-Ivar, you're speculating. And your speculation is wrong. We (Chrome) are releasing a version that supports both old and new format constraints on all 3 getUserMedia versions. So anything that depends on the browser being Chrome will still depend on the browser being Chrome; anything that depends on getUserMedia (unprefixed) parsing new constraints will Just Work (modulo bugs in the new constraints). The fact that there were users being broken by this not working for navigator.mediaDevices.getUserMedia was the reason we withdrew the shipping of that last year. The one category left out in the cold at the moment is the category of those that put in both old and new format into their constraints, expecting Chrome to parse one and Firefox to parse the other. You will find the count of such users here: https://www.chromestatus.com/metrics/feature/timeline/popularity/1389 These scripts will get a TypeError callback / rejected promise. The count of conformant (new-syntax) constraint users is here: https://www.chromestatus.com/metrics/feature/timeline/popularity/1152 And the count of old-style constraint users is here: https://www.chromestatus.com/metrics/feature/timeline/popularity/1150 The numbers are as expected given that it's only been unflagged last week. Once the second counter is significantly larger than the third counter, we'll consider removing support for the old-style constraints. At the moment, the Right Choice is obvious. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/368#issuecomment-227951847 using your GitHub account
Received on Thursday, 23 June 2016 05:14:45 UTC