Stop fetching info from Specref for WICG specs and W3C ED #1633
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
This provides a more generic solution to #1606. Browser-specs has become the main source for Specref for WICG specs and W3C Editor's Drafts. The code no longer attempts to fetch info for these specs from Specref as a result. Tested locally, this will adjust a handful of spec titles (to match the actual spec title, which seems good). Interestingly, it will also adjust a few WICG entries for which the spec says the status is "Unofficial Draft", which will also switch the standing for these specs to "pending". That seems good as well although we may want to review these changes before we release a new version. I propose to do that separately in any case. Specs in that category include: Web Share Target API, preferCurrentTab, the CSS Parser API. Note: Specref is still being used as source, mainly for WHATWG specs.
Filtering drops WICG specs, but also drops W3C EDs.
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.
This provides a more generic solution to #1606.
Browser-specs has become the main source for Specref for WICG specs and W3C Editor's Drafts. The code no longer attempts to fetch info for these specs from Specref as a result.
Tested locally, this will adjust a handful of spec titles (to match the actual spec title, which seems good)... and the URL of element-timing! Interestingly, it will also adjust a few WICG entries for which the spec says the status is "Unofficial Draft", which will also switch the standing of these specs to "pending". That seems good as well although we may want to review these changes before we release a new version. I propose to do that separately in any case. Specs in that category include: Web Share Target API, preferCurrentTab, the CSS Parser API.
Note: Specref is still being used as source, mainly for WHATWG specs.