On 4/21/16 11:00 AM, Richard Barnes wrote:
This is clearly a powerful feature, so it's a natural candidate for
restriction. Chromium is restricting all of navigator.geolocation as of 50:
https://codereview.chromium.org/1530403002/
Just to be clear, Firefox will still allow getCurrentPosition(
This is clearly a powerful feature, so it's a natural candidate for
restriction. Chromium is restricting all of navigator.geolocation as of 50:
https://codereview.chromium.org/1530403002/
Our telemetry shows that only ~0.1% of the usage of watchPosition() is in
non-secure contexts.
http://mzl.l
2 matches
Mail list logo
