[geolocation-api] Effectively no-op step in the “acquire a position” algorithm (suggesting something is wrong) (#134)

triple-underscore has just created a new issue for https://github.com/w3c/geolocation-api:

== Effectively no-op step in the “acquire a position” algorithm (suggesting something is wrong) ==


In the algorithm [acquire a position](https://w3c.github.io/geolocation-api/#dfn-acquire-a-position):

> If cachedPosition's timestamp's value is greater than cacheTime, and cachedPosition.[[isHighAccuracy]] equals options.enableHighAccuracy, set position to cachedPosition.

In this step, the position variable is set to a value, but this value will never be used in the later steps
(there are two other instances of “position”, the first one is under the “Otherwise” clause and is not relevant, the second one is set to a new value);
meaning that this step effectively does nothing and suggesting something is wrong in this algorithm.



Please view or discuss this issue at https://github.com/w3c/geolocation-api/issues/134 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Sunday, 16 April 2023 14:36:42 UTC