track.getSettings - would anyone mind if we made it async?

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

Received on Wednesday, 27 April 2016 09:54:27 UTC