Bug 33762 - navigator.location returns an object even though currently not supported
Summary: navigator.location returns an object even though currently not supported
Status: RESOLVED WORKSFORME
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Linux
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-16 10:11 PST by Sarven Capadisli
Modified: 2010-01-16 11:41 PST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sarven Capadisli 2010-01-16 10:11:03 PST
I'm noticing that navigator.geolocation returns an object and !!navigator.geolocation returns true. If there is no geolocation support, shouldn't it return undefined and false respectively? Also note because Chromium sort of reports that navigator.location is okay, navigator.geolocation.getCurrentPosition() is useless as errorCallback is not used.
Comment 1 Sarven Capadisli 2010-01-16 11:41:55 PST
(In reply to comment #0)
> I'm noticing that navigator.geolocation returns an object and
> !!navigator.geolocation returns true. If there is no geolocation support,
> shouldn't it return undefined and false respectively? Also note because
> Chromium sort of reports that navigator.location is okay,
> navigator.geolocation.getCurrentPosition() is useless as errorCallback is not
> used.

False alarm.