Person merging, please make sure that commits are squashed with one of the following as a commit message prefix:
chore: fixes unrelated to the spec itself (e.g., fix to Github action, html tidy, spec config, etc.).
editorial: a non-normative change to the spec (e.g., fixing an example or typo, adding a note).
change: a normative change to existing engine behavior.
And use none if it's a new normative requirement.
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:
It was ambiguous about whether it rounded to the nearest integer, and new specifications should use the terms in #sec-tools instead.
https://github.com/whatwg/notifications/pull/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