Closed Bug 1134713 Opened 11 years ago Closed 10 years ago

geolocation.clearWatch does not work: watchPosition callbacks still firing

Categories

(Firefox OS Graveyard :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jeremywosborne, Unassigned)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.111 Safari/537.36 Steps to reproduce: * Called watchPosition to do just that. Works great. * Had moments in my app where I need/want to stop watchPosition firing, called clearWatch on id returned by watchPosition. * clearWatch doesn't seem to work, watchPosition still firing. Actual results: * clearWatch doesn't work, watchPosition callbacks still firing. Expected results: watchPosition callbacks should stop firing.
Here's a bit more info to help classify the issue for those of you better at classifying it than me: Target Device Information Model: Flame phone Software: B1TC00011220 OS Version: 1.3.0.0-prerelease Hardware Revision: 01 Platform Version: 28.0 Git commit info: 2014-06-11 01:59:44 e1b71527
ni? on Doug, the module owner
Flags: needinfo?(dougt)
harald, can you verify?
Flags: needinfo?(dougt)
I was able to reproduce the on B2G Desktop from 1.3 to 2.0. It seems to be fixed in 2.1 and above. I verified on a Z3C with 3.0.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: