Re: track.getSettings - would anyone mind if we made it async? from Harald Alvestrand on 2016-04-28 (public-media-capture@w3.org from April 2016)

From: Harald Alvestrand <harald@alvestrand.no>
Date: Thu, 28 Apr 2016 11:18:53 +0200
To: public-media-capture@w3.org
Message-ID: <5721D57D.20307@alvestrand.no>

Den 27. april 2016 11:53, skrev Harald Alvestrand:
> I'm looking at implementing getSettings in Chrome, as part of our
> constraints push.
> 
> It seems that it doesn't exist on my (v45) Firefox either, so backwards
> compatibility isn't a big worry yet.
> 
> For reasons of Chrome's internal architecture, it might be slightly
> simpler if we made it return a promise (so that it's async).
> 
> Would anyone mind if we did that?
> 
> Harald
> 

Update - I think it doesn't matter to Chrome either. Let's keep it as-is
for now.

Received on Thursday, 28 April 2016 09:19:25 UTC