- From: Wanming Lin via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Aug 2018 07:12:31 +0000
- To: public-device-apis-log@w3.org
> As I understood the previous iteration, the initial value of the "mock sensor reading" was selected by the UA, and the WebDriver extension commands allowed developers to modify that value directly. Is that right? Is there some aspect of that architecture which caused problems? @jugglinmike, many thanks for your comments! You're right! What I thought before may be a bit complicated. With both "mock sensor reading" and "default mock sensor reading" is actually confused people, I will leave with "mock sensor reading" only, seems I also miss the timestamp, will add it as well. -- GitHub Notification of comment by Honry Please view or discuss this issue at https://github.com/w3c/sensors/pull/369#issuecomment-417213996 using your GitHub account
Received on Thursday, 30 August 2018 07:12:32 UTC