W3C home > Mailing lists > Public > public-geolocation@w3.org > June 2021

Re: [geolocation-api] Gracefully handle documents that are not fully active (#90)

From: Reilly Grant via GitHub <sysbot+gh@w3.org>
Date: Tue, 15 Jun 2021 00:24:48 +0000
To: public-geolocation@w3.org
Message-ID: <issue_comment.created-861077787-1623716682-sysbot+gh@w3.org>
Maybe I'm missing the issue this change is attempting to fix but what happens after the following sequence of events,

1. Document is fully active.
2. Script calls navigator.geolocation.watchPosition().
3. Document becomes not fully active.
4. A "significant" change in position occurs.
5. Document becomes fully active.

As written it seems like when a significant change in position occurs while the document is not fully active it will cause the watch to be canceled. Is this intentional? More likely it seems like we want to explicitly cancel all pending requests on transition to being not fully active. We definitely don't want to deliver a position update while not fully active but we may want to preserve active watches and check on transition back to fully active whether a significant change in position has occurred.

GitHub Notification of comment by reillyeon
Please view or discuss this issue at https://github.com/w3c/geolocation-api/pull/90#issuecomment-861077787 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 15 June 2021 00:27:05 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 15 June 2021 00:27:09 UTC