W3C home > Mailing lists > Public > public-device-apis-log@w3.org > April 2021

Re: [proximity] Behavior of `distance` attribute when sensor cannot provide distance measurements? (#44)

From: Reilly Grant via GitHub <sysbot+gh@w3.org>
Date: Thu, 08 Apr 2021 06:14:27 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-815479478-1617862465-sysbot+gh@w3.org>
In discussion of this issue at our F2F meeting on April 8th a concern was raised that developers may ignore the `near` attribute if they only test their code on devices which are capable of providing the `distance` attribute. I suggested that to mitigate this the `ProximitySensor` constructor be modified to take a threshold (or even a pair of rising and falling thresholds) that is used to calibrate the definition of "near" for the sensor. Applications would thus be encouraged to use the `near` attribute unless they have a particular need for the more complex `distance` attribute, in which case they likely would either not support or need separate fallback logic for the case where they were running on a device without support for distance measurement.,

GitHub Notification of comment by reillyeon
Please view or discuss this issue at https://github.com/w3c/proximity/issues/44#issuecomment-815479478 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 8 April 2021 06:14:29 UTC

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