- From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
- Date: Thu, 15 May 2014 08:45:03 +0000
- To: Jan-Ivar Bruaroey <jib@mozilla.com>, "bugzilla@jessica.w3.org" <bugzilla@jessica.w3.org>, "public-media-capture@w3.org" <public-media-capture@w3.org>
On 2014-05-15 03:15, Jan-Ivar Bruaroey wrote: > On 5/14/14 8:12 AM, bugzilla@jessica.w3.org wrote: >> There may be situations when getting the data may take some time (e.g. reaching >> out to devices), so we should not stop the main script. (getConstraints should >> be fast) > > Can't all this information effectively be gathered during and cached > beyond the originating gUM or applyConstraint call? If that is possible, that would be a really good. But can't the settings vary over time (even with no changes to the constraints)? > > What's an example where get would need to block? Not sure what you mean, but doing var curSettings = track.getSettings(); or var curNativeSet = track.getNativeSetting(); I would expect to get the currently used settings (not the ones that was used immediately after the latest applyConstraints). > > .: Jan-Ivar :. > > >
Received on Thursday, 15 May 2014 08:45:27 UTC