- From: Sominemo via GitHub <noreply@w3.org>
- Date: Thu, 06 Nov 2025 03:10:02 +0000
- To: public-device-apis-log@w3.org
It seems that you, as a user or developer, are only interested in the foreground access extension, which is perfectly fine and makes sense. The scrutiny from implementers is exactly why there are three different solutions proposed. I'll stress that these are distinct proposals, each good for different use cases and making different trade-offs. You are right that 'backgroundable location' is the easiest path forward for some background access, even if it's not for all use cases. Speaking of the other two, the idea is to learn from existing native consent systems, like permission reminders or automatic retractions, and build on them. Of course, no model can perfectly protect against edge cases like shared devices, but the goal is to bring PWAs closer to native functionality. From a technical perspective, I don't see anything extraordinary in a browser checking the location in the background, filtering events, and passing them to a registered Service Worker callback. -- GitHub Notification of comment by Sominemo Please view or discuss this issue at https://github.com/w3c/geolocation-sensor/issues/22#issuecomment-3494664762 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 6 November 2025 03:10:03 UTC