editorial: Remove the definition of "epoch-relative timestamp". #153
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It was ambiguous about whether it rounded to the nearest integer, and new specifications should use the terms in #sec-tools instead. If I missed cleaning up some existing use, imitate the replacement in the #the-epochtimestamp-typedef section.
5 tasks
jyasskin
commented
Mar 20, 2023
noamr
reviewed
Mar 21, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It was ambiguous about whether it rounded to the nearest integer, and new specifications should use the terms in #sec-tools instead.
whatwg/notifications#192 removes the only use listed in https://dontcallmedom.github.io/webdex/e.html#epoch-relative%20timestamp%40%40hr-time%25%25dfn. If I missed another one, whoever cleans that up can imitate the replacement in that PR or in the #the-epochtimestamp-typedef section here.
Person merging, please make sure that commits are squashed with one of the following as a commit message prefix:
If this is a "change", please explain what's significantly changing.
In particular, if the change results in potential backwards compatibility issues and content breakage, it needs to be justified.
For normative spec changes, please get implementation commitments anf file issues on the various engines during the review process. All tasks should be complete before merging.
Implementation commitment - primarily for "change" and other normative changes:
Tasks:
Preview | Diff