635175 - navigator.geolocation.getCurrentPosition error callback not fired

Status: VERIFIED DUPLICATE of bug 591745

(Core :: DOM: Geolocation, defect)

Description

[Michal Kubik]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101206 Ubuntu/10.04 (lucid) Firefox/3.6.13
Build Identifier: Mozilla/5.0 (X11; Linux i686; rv:2.0b11) Gecko/20100101 Firefox/4.0b11

I experienced the same problem as described in Bug 538792. When using getCurrentPosition asynchronous onSucces function is called twice. It doesn't in Chrome or IE.
checked on FF 3.6.13 UA: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101206 Ubuntu/10.04 (lucid)

I decided to checked it on new FF 4.0 beta 10 if it is corrected and it's even worse. OnSuccesHandler function is called once but after some time(probably timeout used for geolocation) OnErrorHandler function is called. I updated to FF 4.0 beta 11 and this seems to be fixed but
additionally when asked to share location if we choose "Not Now" onErrorHandler is not executed at all.
Checked with FF 4.0b11 UA: Mozilla/5.0 (X11; Linux i686; rv:2.0b11) Gecko/20100101 Firefox/4.0b11

Reproducible: Always

Steps to Reproduce:
1. use navigation.geolocation.getCurrentPosition on your page
2. choose not to share your location - onError should be fired

Actual Results:  
onError function is not executed

Expected Results:  
onError function should fire

geolocation is important feature nowadays. Maybe not on stationary device but stationary device is helpful in mobile testing.

Comment 1

[Josh Matthews [:jdm]]

I'm pretty sure this is by design.  "Not now" is just a way of hiding the dialog box; if you trigger "Never share" or if a timeout occurs, then the error callback should be triggered.

Comment 2

[Michal Kubik]

I would agree if "Not Now" would be a way to just terminate location acquiring process. But I'm not sure if it is how "Not Now" should work. I would expect it to work like "Don't Share" button in FF 3.6.

When page author designs geolocation he have to predict two situations success and fail in obtaining position In case of fail error code could be used to determine for example Permission Deny.

Now we have also situation "terminated" to handle. So "Not Now" should work like earlier "Don't Share". I don't see any idea changing it, but maybe there is something behind it.

Comment 3

[Josh Matthews [:jdm]]

Nope, Not Now is just a way of hiding the geolocation popup.  You'll note that the popup can be retrieved at any time by clicking the icon beside the favicon, so we don't actually give any action for pressing it.

Comment 4

[Michal Kubik]

Oh yes, I have found that small cross-hair pointer icon. It seems to be nice feature as when I click somewhere beside popup it hides but icon remains. Anyway I still deem that it would be more straightforward if "Not Now" would be one time denial. 

Maybe my page could bring you round to my idea: http://t119.pl.volantis.com/mcs/rVMS-2935/geolocationAPI.xdime .  Terminating acquisition process makes my button disabled while I should get error and enable them back.

Comment 5

[Josh Matthews [:jdm]]

1) Please stop changing the status of this bug.  I have marked it invalid for a reason; the reason being that this is by design.
2) Duping.

Comment 6

[Michal Kubik]

sorry Josh, I though we are just discussing this way. I agree it's duplicate. 
It confirms I'm not the only one confused by this "by design".