Don't fetch info from Specref for CSS and www.w3.org specs. #1658
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 still fetched info from Specref for a few W3C specs, notably the
css-backgrounds-4
draft and a few policy documents. Info is now fetched directly from the spec for these specs. This will make it possible to properly retirecsswg.json
in Specref.The GIF spec, published under
https://www.w3.org
is treated as an exception to the rule, because its URL ends with.txt
, signaling a spec published in plain text.Note: Browser-specs still leverages Specref, mainly for WHATWG specs, a few TC39 and ISO specs, and a couple of CG specs that use their own GitHub org.