> Would be nice to bring that implementer feedback to the table, so the group can discuss the different options suggested and get consensus around them.
yeah, I notified the group on the call yesterday.
> From what I see, the conversation seems focused on 60Hz, but we do want to get faster than that. What will happen then? Etc.
The problem described in [the bug](https://bugs.chromium.org/p/chromium/issues/detail?id=715872) is that we cannot use rAF mechanism to sync sending updates for a sensor regardless of the frequency.
60Hz limit is an implementation detail in Chromium and it is not related to this PR. This PR is fixing concrete problems for the existing operations.
> I think it would be useful to open a new issue with this. Sumarize the issues, the different proposals, etc.
Wouldn't the existing https://github.com/w3c/sensors/issues/171 fit?
--
GitHub Notification of comment by pozdnyakov
Please view or discuss this issue at https://github.com/w3c/sensors/pull/197#issuecomment-302625123 using your GitHub account