[Bug 20307] in HTML should warn when title precedes meta@charset

https://www.w3.org/Bugs/Public/show_bug.cgi?id=20307

--- Comment #6 from Daniel.S <crazy-daniel@gmx.de> ---
(In reply to comment #5)
> http://validator.w3.org/nu/ is the current validator service. It is the only
> W3C validator service that's being actively maintained, and that has any new
> bug fixes going into it. It is called the "W3C Nu Markup Validation Service".

Thanks for explaining.

> http://validator.w3.org/ is the legacy validator service. I do not work on
> the code for that. Nobody does any longer, because it's not being actively
> maintained. It has a feature that allows checking of HTML5 documents, but
> all that feature does is that it calls the http://validator.w3.org/nu/
> service behind the scenes.

I don't think that there are a lot of people who are actually aware of this.

> If they are errors about how it handles HTML5 documents, nowhere. Because
> the only service for which HTML5 checking is now supported is
> http://validator.w3.org/nu/ So if you want to check HTML5 documents, use
> http://validator.w3.org/nu/ directly. Or even if you want to check HTML4
> documents -- it can check those fine too.
> 
> Don't use http://validator.w3.org/

I'm a little shocked by the obviousness your statment implies.

This is the first time I hear about this state of http://validator.w3.org/
Please tell me if I'm living in an ivory tower, but I don't know anyone who's
using http://validator.w3.org/nu/ or even advocate its use (few use
validator.nu though).

A lot of questions come to my mind, for example, why is there no public or
official note in this? What are the future plans for http://validator.w3.org/?
Are there any? I didn't do an in-depth search, but the impact of this
information appears so to be so big that it should be easily discoverable.

Well, I'll start to use and advocate http://validator.w3.org/nu/ from now on.

If you got any answers for me, it'd be ok to send them to me privately if you
feel they don't belong to this place. Again, thanks for explaining.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 23 April 2013 11:51:01 UTC