Fix browser-specs script for IETF drafts #768
Merged
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
Browser-specs contributes IETF drafts that have not yet been published as RFC to Specref. A recent update made to browser-specs flag such entries as coming from an "ietf" source (because the code gets the info from datatracker.ietf.org. The browser-specs script needed to be updated in Specref to account for this new source.
dontcallmedom
approved these changes
Dec 5, 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.
Browser-specs contributes IETF drafts that have not yet been published as RFC to Specref. A recent update made to browser-specs flag such entries as coming from an "ietf" source (because the code gets the info from datatracker.ietf.org.
The browser-specs script needed to be updated in Specref to account for this new source.