[Webkit-unassigned] [Bug 186689] New: Position timestamp returns from geo api doesn't reflect the current time

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=186689

            Bug ID: 186689
           Summary: Position timestamp returns from geo api doesn't
                    reflect the current time
           Product: WebKit
           Version: Safari 10
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: roderickhsiao at gmail.com

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

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20180615/06975f2f/attachment.html>