Skip to content
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

Again #43

Open
matsaman opened this issue Feb 28, 2019 · 0 comments
Open

Again #43

matsaman opened this issue Feb 28, 2019 · 0 comments

Comments

@matsaman
Copy link

Following #35 (which I just found),
#42 (which I took the time to file),
and 1b12fe4
... I must say, you really need to not have a validator on w3.org that validates against a spec other than w3.org's.

I see that commit is from 2015, when perhaps it was appropriate, I don't know, and it doesn't matter.

The fact of the matter is that right now w3.org has an HTML5 recommendation specification, and w3.org has a markup validator that validates HTML5 against an altogether different specification living on an entirely separate website purportedly run by an entirely separate competing organization.

This is obviously not useful. At least one of the following three things in the least should happen:

  1. The validator on w3.org should validate against w3.org's spec
  2. The spec on w3.org should cease to be and the other spec should be endorsed
  3. There should be a comment on this issue tracker from a representative willfully stating that neither 1 nor 2 will be done (this would at least acknowledge to people that you aren't really confused, and instead just have a particular plan you are following)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant