- From: Tom333Trinity via GitHub <sysbot+gh@w3.org>
- Date: Thu, 06 May 2021 05:17:07 +0000
- To: public-geolocation@w3.org
What happen to "Happy to chat,"? WRT @jyasskin and "consensus across browser engines," I must have missed a link to the consensus vote for https://github.com/w3c/geolocation-sensor/issues/44 could you provide one please? And let's see, if we follow your [link ](https://discourse.wicg.io/t/proposal-expose-geolocation-to-service-workers/2588) we come to: - > @JaiOwl, thanks for your input. This topic has graduated from incubation and the work is now underway in the Devices and Sensors Working Group. You can help by reviewing the Geolocation Sensor use cases that consider both foreground and background operations enumerated at https://w3c.github.io/geolocation-sensor/#use-cases 176 and submit feedback via https://github.com/w3c/geolocation-sensor/issues 110 Which inevetibly leads to w3c/geolocation-sensor#44 So I guess, once more, you're asking me to go fetch a left-handed screw driver or a tin of striped paint? For *another* 5 years? @marcoscaceres I'm happy for you to move the conversation anywhere the free exchange of ideas can take place! But it is my great lament that a working example [SSCCE](https://github.com/RichardMaher/Brotkrumen) has been wilfully ignored for so long :-( Tell me what is wrong with it????? Anyway I will add a Screen Lock to BrotKrummen to make it easier to demonstrate and get back. -- GitHub Notification of comment by Tom333Trinity Please view or discuss this issue at https://github.com/w3c/geolocation-api/issues/74#issuecomment-833231720 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 6 May 2021 05:17:10 UTC