- From: Reilly Grant via GitHub <sysbot+gh@w3.org>
- Date: Tue, 21 May 2024 01:24:31 +0000
- To: public-device-apis-log@w3.org
I've always interpreted `interval` as a promise to fire the event at a particular implementation-defined rate. That is, `timestamp` tells you when the event was generated and `interval` tells you when to expect the next one. This is important for motion events because they represent rates of change. Note that `devicemotion` events are fired at a fixed interval while `deviceorientation` events (which represent a position rather than a change in position) fire whenever there is significant change. -- GitHub Notification of comment by reillyeon Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/185#issuecomment-2121528391 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 21 May 2024 01:24:32 UTC