See: http://dev.w3.org/geo/api/spec-source.html#coordinates The current implementation returns 0 or -1.
<rdar://problem/6713745>
Created attachment 29426 [details] patch channeled by Sam This is from the beginnings of a patch from Sam. I've added it to support the 4 Coordinates properties that are null if they cannot be provided.
Comment on attachment 29426 [details] patch channeled by Sam Seems to me that since these are doubles we could have used NaN instead of separate booleans to initialize the Coordinates object. r=me
bolsinga:WebKit bolsinga$ svn commit Sending WebCore/ChangeLog Sending WebCore/GNUmakefile.am Sending WebCore/WebCore.pro Sending WebCore/WebCore.scons Sending WebCore/WebCore.vcproj/WebCore.vcproj Sending WebCore/WebCore.xcodeproj/project.pbxproj Sending WebCore/WebCoreSources.bkl Adding WebCore/bindings/js/JSCoordinatesCustom.cpp Sending WebCore/page/Coordinates.h Sending WebCore/page/Coordinates.idl Sending WebCore/platform/mac/GeolocationServiceMac.mm Transmitting file data ........... Committed revision 42437.