Skip to content

Switch DOMTimeStamp to EpochTimeStamp #104

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Oct 12, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@
</script>
</head>
<body data-cite=
"secure-contexts permissions-policy permissions page-visibility-2">
"secure-contexts permissions-policy permissions page-visibility-2 hr-time">
<section id="abstract">
<p>
The Geolocation API provides access to geographical location
Expand Down Expand Up @@ -674,8 +674,7 @@ <h2>
position</dfn>.
<ol>
<li>Let |acquisitionTime:DOMTimeStamp| be a new
{{DOMTimeStamp}} that represents now in milliseconds, using
01 January, 1970 UTC as the epoch.
{{EpochTimeStamp}} that represents now.
</li>
<li>If |options|.{{PositionOptions/maximumAge}} is greater
than 0, and |cachedPosition| is not null:
Expand Down Expand Up @@ -923,7 +922,7 @@ <h2>
[Exposed=Window, SecureContext]
interface GeolocationPosition {
readonly attribute GeolocationCoordinates coords;
readonly attribute DOMTimeStamp timestamp;
readonly attribute EpochTimeStamp timestamp;
};
</pre>
<section>
Expand Down