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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This mechanism for preserving the IDs is clever. We should do the same thing for any other cases where we’re moving something out of a spec, and maybe consider documenting it somewhere as a best practice (though I don’t know often this case comes up). Among other reasons, it ensures any existing links in the Specifications tables in MDN articles still bring readers to the point in the document where they need to be (in this, to the statement that the content’s been moved to the HTML spec).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We've been doing it in HTML when moving things around, and Bikeshed has
oldids=""
(https://tabatkins.github.io/bikeshed/#id-gen). There might even be something similar in ReSpec, but I'm not as familiar...