- From: Chris Dumez via GitHub <sysbot+gh@w3.org>
- Date: Tue, 29 Jan 2019 17:13:45 +0000
- To: public-geolocation@w3.org
@anssiko What sort of feedback are you looking for? I filed this issue so requestPermission() is definitely sometime we want and it would definitely be a better situation than having the API disabled by default. @annevk was also on board with such API, so that's 2 implementers. If Blink wants to keep providing access to the API without user consent, this is fine, the requestPermission() could always be a no-op for them. @larsgk FYI, third-party content already does not have access to the API in WebKit so this discussion is about first party for us. Also note that the whole reason we want a permission API is to avoid over-prompting the user since there is a lot of content out there already using the API but not actually requiring it (e.g. tracking). With regards to Web Applications (PWA), we'll need to discuss this internally, this is more of a system policy and I do not think this should be spec'd. -- GitHub Notification of comment by cdumez Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/57#issuecomment-458625461 using your GitHub account
Received on Tuesday, 29 January 2019 17:13:47 UTC