Home/ Questions/Q 8094079
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-05T20:40:48+00:00

I am creating a website that uses W3C Geolocation API and position.timestamp for timestamp.

  • 0

I am creating a website that uses W3C Geolocation API and position.timestamp for timestamp. I have tested it on Safari 5.1.6 (Mac OS X Lion) and iPhone (5.x). iPhone default browser returns correct value for timestamp, while Safari does not. Has anyone experience similar issue? Is there a bug in Safari?

Test it here: http://jsfiddle.net/vRRdE/2/

Running the test above (thanks Tyilo) I get 360419807893 (wrong one using position.timestamp) and 1338727007910 (correct one using Date().getTime()) using Safari on Mac OS X.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It seems that desktop Safari uses January 1, 2001 as the default epoch so the best approach here is probably just using Date().getTime();

    • 0