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

Web developers with devices capable of measuring `distance` might only rely on the value, breaking the app when used on devices with only near/far boolean.  Could it make sense to introduce an enum, e.g  `MIN`, `NEAR`, `MIDDLE`, ... `FAR`, `UNDEFINED`, encouraging developers to use values not causing unintended behavior?

-- 
GitHub Notification of comment by larsgk
Please view or discuss this issue at https://github.com/w3c/proximity/issues/44#issuecomment-815483336 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:22:04 UTC