-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Nu HTML Checker #6843
Comments
@sideshowbarker can help with the substantive claim here. As for "has no place in a standard", we disagree. It seems, based on this and other issues, you are not used to how modern standards-setting is done. Thankfully you've come to the right place to learn and be corrected by an expert community! |
domenic that's pretty funny. The last time I checked, W3C's work yielded a less than 1% of websites on the web being standard-compliant. What number has WHATWG got it up to? |
Where is it even referenced? |
https://html.spec.whatwg.org/#how-to-catch-mistakes-when-writing-html:-validators-and-conformance-checkers links to https://whatwg.org/validator/ . I misremembered and though there were two validators listed on that page, which might have made this issue interesting if the other validator was better. In fact now there is just one validator; the other was removed in whatwg/whatwg.org@be5d39e . So I will close this. |
Nu HTML Checker needs to be removed as a conformance checker from the standard. Nu HTML Checker is a beta and therefore by definition is incomplete and has no place in a standard.
WHATWG's conformance checker is complete so Nu HTML Checker just over complicates things. Cutting down irrelevant stuff in the standard is important as time is valuable. Many web developers won't take note of the standard if they find it overwhelming and will instead turn to shitty non-authoritive HTML teaching sources.
The text was updated successfully, but these errors were encountered: