Switch from browser-specs to web-specs #869
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
The `web-specs` package contains non browser specs on top of the specs that target browsers in the `browser-specs` package. Whether a spec targets browsers or not will appear in the crawl results under the `categories` property.
dontcallmedom
approved these changes
Feb 8, 2022
|
Tests need an update |
|
Yes, saw that :) |
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.
The
web-specspackage contains non browser specs on top of the specs that target browsers in thebrowser-specspackage.Whether a spec targets browsers or not will appear in the crawl results under the
categoriesproperty.Follows from w3c/browser-specs#436 and w3c/browser-specs#496