On Sat, Oct 22, 2016, at 09:38 PM, Richard Barnes wrote: > On Fri, Oct 21, 2016 at 5:56 PM, Ehsan Akhgari <ehsan.akhg...@gmail.com> > wrote: > > Since the proposal in the bug is adding [SecureContext] to > > Navigator.geolocation, have we also collected telemetry around which > > properties and methods are accessed? Since another kind of breakage we > > may encounter is code like |navigator.geolocation.getCurrentPosition()| > > throwing an exception and breaking other parts of site scripts... > > > > I'm not picky about how exactly we turn this off, as long as the > functionality goes away. Chrome and Safari both immediately call the > error handler with the same error as if the user had denied permission. We > could do that too, it would just be a little more code.
I would be OK with this change if it is implemented in a way compatible with Chrome and Safari. Looks like they both call the error handler and show an error in the console when the request is denied. And it should be behind a pref so we can monitor it's usage during the release cycle. Kanru _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
