- From: Philip Jägenstedt via GitHub <sysbot+gh@w3.org>
- Date: Fri, 16 Dec 2016 13:00:59 +0000
- To: public-device-apis-log@w3.org
In fixing this, the precise timing of when data changes should also be defined. In https://codereview.chromium.org/2551223003/ there's a change to make the change itself and the event aligned with animation frames, and maybe that's what you want. FWIW, it's not obvious to me that this *is* what you want. If you have a sensor that produces data faster than animation frames and that data is used to influence Web Audio, faster than 60 Hz could make sense. -- GitHub Notification of comment by foolip Please view or discuss this issue at https://github.com/w3c/sensors/issues/152#issuecomment-267589331 using your GitHub account
Received on Friday, 16 December 2016 13:01:05 UTC