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

Re: [sensors] DOMExceptions when calling stop/start on already stopped/started sensor

From: Tobie Langel via GitHub <sysbot+gh@w3.org>
Date: Fri, 27 Jan 2017 17:02:34 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-275716690-1485536552-sysbot+gh@w3.org>

> you can check the state if you really want to check if it stopped 
correctly.

That was a late friday afternoon attempt at humour. Sorry. :-/

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

Received on Friday, 27 January 2017 17:02:40 UTC

This message: [ Message body ]
Next message: Tobie Langel via GitHub: "Closed: [sensors] DOMExceptions when calling stop/start on already stopped/started sensor"
Previous message: Tobie Langel via GitHub: "Re: [sensors] Find a better name for 'unconnected' state"
In reply to: Alexis Menard via GitHub: "[sensors] DOMExceptions when calling stop/start on already stopped/started sensor"
Next in thread: Tobie Langel via GitHub: "Closed: [sensors] DOMExceptions when calling stop/start on already stopped/started sensor"

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:53 UTC