- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Sat, 24 Jun 2017 04:19:21 +0000
- To: public-media-capture-logs@w3.org
> I believe current implementations just pass the values to the OS-level APIs and read them back accordingly @dsanders11 That's too expensive because `track.getSettings()` is synchronous. In Firefox at least, we don't access devices on the main thread. Instead we queue a task on the main thread when state changes, to store it there, where JS can read it. Regardless, even if we accessed it directly, the only state we'd need to round values before returning them is `track.getConstraints()` which is already stored state according to the spec. Adding complexity to implementations is warranted if it removes complexity for users. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-image/pull/182#issuecomment-310812868 using your GitHub account
Received on Saturday, 24 June 2017 04:19:27 UTC