I understand this is not great UX, from a user perspective some sites
used to work and they don’t anymore. There is not much we can do about
it though: the web engine the browser app uses is based on chromium, and
chromium is intentionally denying geolocation requests on insecure
origins starting with version 50. See
https://bugs.chromium.org/p/chromium/issues/detail?id=561641 for a
detailed discussion.
I verified that chromium on desktop and chrome on android behave exactly the
same: they deny the geolocation request.
Firefox currently accepts them, but I read somewhere that they are considering
deprecating the feature in the same manner, so it’s only a matter of time
before the feature stops working there too.
Note that before blocking the feature, it had been marked deprecated
long in advance, and web developers would get a message in the
javascript console warning that the feature would eventually be blocked.
metoffice.gov.uk and streetmap.co.uk have ignored that warning, and that
results in bad UX. This is unfortunate, but again there is not much we
can do about it (nothing really), as we’re not getting a signal from
chromium that a request has been denied because it originated from an
insecure origin.
Thanks for forwarding the info to the UK met office, I’m sure they’ll
consider addressing it asap.
** Changed in: webbrowser-app (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1588500
Title:
Applications with permission for location claim they don't
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1588500/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
