- From: Jens Oliver Meiert <jens@meiert.org>
- Date: Sun, 29 Oct 2023 15:51:45 +0000
- To: "Jukka K. Korpela" <jukkakk@gmail.com>
- Cc: W3C WWW Validator <www-validator@w3.org>
> I suppose the purpose is good: analyze and report anything that might be a problem and inform the user about them, whether it is HTML, HTTP, CSS, JavaScript, or whatever, But it may and will confuse people who think that a program named “Nu Html Checker” should check HTML, and just HTML Yes, and for that we probably had the Unicorn validator [1]. As lack of resources was cited to have led to that validator’s shutdown [2], perhaps the team can comment on the resource situation and plan for the scope of the HTML validator? A quick note, Jukka—I didn’t spell it out in the original mail, but I did refer to *CSP* (content security policy) errors thrown by the HTML validator. I agree that CSS validation comes surprising in the HTML validator, too, but my main concern is that by reporting and counting CSP errors, it’s even harder to analyze the HTML. [1] https://www.w3.org/2023/03/31-unicorn-discontinued [2] https://www.w3.org/news/2023/w3c-sun-setting-online-unified-validator-community-may-fork-unicorn/ -- Jens Oliver Meiert https://meiert.com/en/ · https://mas.to/@j9t
Received on Sunday, 29 October 2023 15:52:10 UTC