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

Re: [accelerometer] Why unrestricted double for acceleration readings?

From: Mikhail Pozdnyakov via GitHub <sysbot+gh@w3.org>
Date: Wed, 20 Sep 2017 08:54:14 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-330789010-1505897643-sysbot+gh@w3.org>

Think it was supposed to mean "unset value" but now the reading properties are nullable so no need to keep them `unrestricted`.

-- 
GitHub Notification of comment by pozdnyakov
Please view or discuss this issue at https://github.com/w3c/accelerometer/issues/23#issuecomment-330789010 using your GitHub account

Received on Wednesday, 20 September 2017 08:54:09 UTC

This message: [ Message body ]
Next message: Anssi Kostiainen via GitHub: "Re: [sensors] Fix Bikeshed custom header rendering bug"
Previous message: Mikhail Pozdnyakov via GitHub: "Re: [sensors] Define sensor.hasReading accessor bound to [[lastEventFiredAt]]. Fixes gh-269"
In reply to: Dominique Hazael-Massieux via GitHub: "[accelerometer] Why unrestricted double for acceleration readings?"
Next in thread: Mikhail Pozdnyakov via GitHub: "Re: [accelerometer] Why unrestricted double for acceleration readings?"

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