W3C home > Mailing lists > Public > public-device-apis-log@w3.org > May 2017

[sensors] Define tasks for state changes

From: Alexander Shalamov via GitHub <sysbot+gh@w3.org>
Date: Sat, 27 May 2017 11:20:48 +0000
To: public-device-apis-log@w3.org
Message-ID: <issues.opened-231795077-1495884046-sysbot+gh@w3.org>
alexshalamov has just created a new issue for https://github.com/w3c/sensors:

== Define tasks for state changes ==
At the moment, spec has [few](https://w3c.github.io/sensors/#sensor-start) [places](https://w3c.github.io/sensors/#sensor-stop) where state is updated without task or (state change + simple event) is fired outside of task execution scope.
 
According to [recommendations from Anne](https://github.com/w3c/sensors/issues/215#issuecomment-304396775) state changes should be performed from task.
 
Also, spec must define what happens to tasks that are in the queue, e.g., whether those can be cancelled (removed from queue).
 
Example 1:
 
Sensor is active and update reading is queued, then error occurs and page loses visibility.
Now we have 3 tasks in queue [update sensor reading, onerror, state change to idle].

Should we process queue and don’t allow new tasks to be added from sensor? Should we 'suspend' tasks and wait when page gains visibility and then process tasks?
 
Example 2:
 
Sensor is is active, update sensor reading scheduled, then stop is called.

Two tasks in queue [update sensor reading, change state to idle]
Should we cancel queued update?


Please view or discuss this issue at https://github.com/w3c/sensors/issues/218 using your GitHub account
Received on Saturday, 27 May 2017 11:20:54 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 12:18:53 UTC