Comment 2 for bug 1592098

A spent a bit of time investigating this report, and I believe that, if indeed there's a bug, that's in Oxide: the handling of maximumAge happens entirely in the Oxide/Chromium code, because the maximumAge parameter is not even being passed to the location service.

In any case this is puzzling because maximumAge default value is already 0, so setting it to 0 shouldn't have any effect at all.