- From: Jeffrey Yasskin via GitHub <sysbot+gh@w3.org>
- Date: Tue, 12 Sep 2023 03:12:58 +0000
- To: public-geolocation@w3.org
jyasskin has just created a new issue for https://github.com/w3c/geolocation-api: == Position data isn't passed into 'new GeolocationPosition' == [Acquire a position](https://w3c.github.io/geolocation-api/#dfn-acquire-a-position) says to "try to acquire position data", and later it says "Set position be a new GeolocationPosition passing acquisitionTime and options.enableHighAccuracy." without mentining that position data. [new GeolocationPosition](https://w3c.github.io/geolocation-api/#dfn-a-new-geolocationposition) then says "Initialize coord's latitude attribute to a geographic coordinate" without giving any indication of what the coordinate should be. These should be wired up. I'd speculate that the flexibility in [new GeolocationPosition](https://w3c.github.io/geolocation-api/#dfn-a-new-geolocationposition) might have originally been to allow users to override their real position, but that should probably be handled in [request a position](https://w3c.github.io/geolocation-api/#dfn-request-a-position) by where permission is handled. While someone's touching this, I also note that several of the steps after "if _position_ is not _cachedPosition_" should actually be conditional on that, and not run when _position_ has been set to _cachedPosition_. Please view or discuss this issue at https://github.com/w3c/geolocation-api/issues/137 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 12 September 2023 03:13:01 UTC