Kingsquare HTML Validator

A HTML5 validation library, using a JavaScript port of the excellent TIDY library

Total ratings

2.86 (Rating count: 36)

Review summary

These summaries are automatically generated weekly using AI based on recent user reviews. Chrome Web Store does not verify user reviews, so some user reviews may be inaccurate, spammy, or outdated.
Pros
  • Incorporated into dev tools, which is great.
  • Works offline.
  • Provides validation by line number.
Cons
  • Does not effectively check or validate HTML content.
  • Errors and warnings can be spurious or misleading.
  • Output format is poor and lacks context around warnings and errors.
  • Struggles with UTF-8 encoded characters.
Most mentioned
  • Does not seem to check anything or produce useful information.
  • Horrible output format.
  • Issues with false warnings and errors.
  • Requires reloading pages to update validations.
See reviews for Kingsquare HTML Validator on Chrome Web Store
Upgrade to see all 38 reviews

User reviews

Recent rating average: 2.40
All time rating average: 2.86
Upgrade to see all 38 reviews

Rating filters

5 star
0%
4 star
32% (12)
3 star
32% (12)
2 star
21% (8)
1 star
16% (6)
Date Author Rating Lang Comment
2019-02-28 Patrick Gallagher Might like it if I could get it to do something. Does not seem to check anything.
2019-02-28
Patrick Gallagher
en Might like it if I could get it to do something. Does not seem to check anything.
2017-11-27
Lodewijk Abrahams
Why does this module not qualified the display video's at the nu.nl?
2017-11-27
Lodewijk Abrahams
en Why does this module not qualified the display video's at the nu.nl?
2016-06-23
Paul Brown
too finicky Should just show errors
2016-06-23
Paul Brown
en too finicky Should just show errors
2015-10-28
maksim
Good plugin, but the output format is **horrible**...
2015-10-29
maksim
en Good plugin, but the output format is **horrible**...
2015-10-15
Raymond DeCampo
Tried this on a site that passed the W3C validator and got spurious warnings (e.g. no DOCTYPE even though DOCTYPE existed, warnings about leftmargin on <body> when there was no such atribute). Also does not work on AJAX sites as far as I could see. Final nail is that if developer tools were not already open, requires a reload to validate.
2015-10-15
Raymond DeCampo
en Tried this on a site that passed the W3C validator and got spurious warnings (e.g. no DOCTYPE even though DOCTYPE existed, warnings about leftmargin on <body> when there was no such atribute). Also does not work on AJAX sites as far as I could see. Final nail is that if developer tools were not already open, requires a reload to validate.
Upgrade to see all 38 reviews