- From: Yoav Weiss via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Jul 2020 18:10:20 +0000
- To: public-geolocation@w3.org
> I don't agree that it's a UX flow issue; it seems very easy to address the issue in a way that does not involve UX. Spec could easily say "location permissions MUST NOT last longer than 24 hours", or any number of other things. Note that I said "UX" and not "UI". Revoking permissions after X hours is most definitely a User Experience flow issue. > Only recording intent / RECOMMENDS does not achieve the above. Nor would an un-testable MUST. (Or a testable MUST, to that effect) Specifications are descriptive, not prescriptive. They don't have magical powers that will force people to do what's written in them. Their role is to outline what's implemented and what needs to be implemented in order to achieve an interoperable web. Landing a testable MUST restriction that's *not implemented by any browser* and that no browser is interested in implementing will only result in that MUST restriction ending up being "at risk" and then removed from the spec. If that MUST restriction is not testable, it may slip through the cracks and stick, but that doesn't mean any implementation would actually follow it, unless they think it makes sense. -- GitHub Notification of comment by yoavweiss Please view or discuss this issue at https://github.com/w3c/geolocation-api/issues/47#issuecomment-652570499 using your GitHub account
Received on Wednesday, 1 July 2020 18:10:22 UTC