Bug 33762

Summary: navigator.location returns an object even though currently not supported
Product: WebKit Reporter: Sarven Capadisli <info>
Component: WebCore Misc.Assignee: Nobody <webkit-unassigned>
Status: RESOLVED WORKSFORME    
Severity: Normal    
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: PC   
OS: Linux   

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.