Closed Bug 1214482 Opened 10 years ago Closed 7 years ago

navigator.geolocation often fails with non zero maxage

Categories

(Firefox for Android Graveyard :: General, defect)

Product:
Firefox for Android Graveyard
Component:
General
Version:
53 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INACTIVE

People

(Reporter: zac.spitzer, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:41.0) Gecko/20100101 Firefox/41.0 Build ID: 20150929144111 Firefox for Android Steps to reproduce: On Firefox for Android v 41.0 a navigator.geolocation.getCurrentPosition request with a non zero maxage ( i.e maxage:2000) fails with a timeout, whilst a maxage:0 works here is a test harness https://jsbin.com/nupuyo/edit?html,console,output 1. click "low (age:2000)", it will return "Position acquisition timed out" 2. reload the page 3. click "low (age:0)" it will return a position Expected results: Max age shouldn't affect whether a position is returned
Component: Untriaged → General
Product: Firefox → Firefox for Android
Version: 41 Branch → Firefox 41
Still happening in Firefox 53
Version: 41 Branch → 53 Branch
Closing per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195 Contact :susheel if you think this bug should be re-opened
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INACTIVE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.