Bug 186689 - Position timestamp returns from geo api doesn't reflect the current time
Summary: Position timestamp returns from geo api doesn't reflect the current time
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: Safari 10
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-15 13:14 PDT by Roderick
Modified: 2018-06-15 13:14 PDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Roderick 2018-06-15 13:14:21 PDT 
Tested both on Safari 10 and 11, 

According to the spec, 
https://developer.mozilla.org/en-US/docs/Web/API/Position/timestamp

The Position.timestamp read-only property, a DOMTimeStamp object, represents the date and the time of the creation of the Position object it belongs to. The precision is to the millisecond.

However, the timestamp returns from Safari its something like 550786249369, which is Mon Jun 15 1987 13:10:49 GMT-0700 (PDT)
But Date.now() returns 1529093495687 which is Fri Jun 15 2018 13:11:35 GMT-0700 (PDT) 

There are a 31 years off