- From: Reilly Grant via GitHub <sysbot+gh@w3.org>
- Date: Tue, 09 Apr 2024 16:55:37 +0000
- To: public-geolocation@w3.org
When building automation for sensors we found that having it "set" the sensor value makes it easier to write tests because the "echo" behavior is prone to race conditions. The "set" semantics are also easier to define in terms of the existing specification algorithms as we can hook into the [acquire a position](https://w3c.github.io/geolocation-api/#dfn-acquire-a-position) steps with "Has an override value been provided, if so return it" rather than introducing language which has to check "are we trying to acquire position? If so, here's a value to return. Otherwise, throw it away?" -- GitHub Notification of comment by reillyeon Please view or discuss this issue at https://github.com/w3c/geolocation-api/issues/146#issuecomment-2045662086 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 9 April 2024 16:55:38 UTC