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

Re: [sensors] Define tasks for state changes

From: Tobie Langel via GitHub <sysbot+gh@w3.org>
Date: Sat, 27 May 2017 11:30:52 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-304446353-1495884651-sysbot+gh@w3.org>

We'll see what the simplest solution to this is.

Given the reason of suspension (mitigate skimming) eventually allowing one reading to come through isn't an issue.

-- 
GitHub Notification of comment by tobie
Please view or discuss this issue at https://github.com/w3c/sensors/issues/218#issuecomment-304446353 using your GitHub account

Received on Saturday, 27 May 2017 11:30:59 UTC

This message: [ Message body ]
Next message: Alexander Shalamov via GitHub: "Re: [sensors] Define algorithm for suspending / resuming activated sensor objects"
Previous message: Alexander Shalamov via GitHub: "Re: [sensors] Clarify relationship between Sensor object and task source"
In reply to: Alexander Shalamov via GitHub: "[sensors] Define tasks for state changes"
Next in thread: Tobie Langel via GitHub: "Re: [sensors] Define tasks for state changes"

Mail actions: [ respond to this message ] [ mail a new topic ]
Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]
Help: [ How to use the archives ] [ Search in the archives ]

This archive was generated by hypermail 2.4.0 : Monday, 4 July 2022 12:47:54 UTC