-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add linter for incorrect feature statuses #15889
Conversation
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.
A bunch of comments here would apply to all lint code. If you think they make sense but don't want to fix it now, can you file issues?
This pull request has merge conflicts that must be resolved before we can merge this. |
1 similar comment
This pull request has merge conflicts that must be resolved before we can merge this. |
This pull request has merge conflicts that must be resolved before we can merge this. |
2 similar comments
This pull request has merge conflicts that must be resolved before we can merge this. |
This pull request has merge conflicts that must be resolved before we can merge this. |
This pull request has merge conflicts that must be resolved before we can merge this. |
This pull request has merge conflicts that must be resolved before we can merge this. |
This pull request has merge conflicts that must be resolved before it can be merged. |
This PR builds on #6813 that starts cherry-pick from #11430 and fixes #6812 to add more status tests, enforcing the following:
true
if there is a spec URLfalse
if a feature is supported in multiple browser enginesThis PR also performs the fix using the provided fix script.