Validity

It stopped working. They must remove it from the Chrome Web Store.

Works fantastically, speeds up my validation workflow by an order of magnitude

12/10 would validate again

Getting "The character encoding was not declared. Proceeding using “windows-1252”." for all websites. Particularly, mine does declare UTF-8

very good

Doesn't work. Complains about character encoding not declared. But it is declared and W3-Validator shows no problems. So: Useless Extension

the instruction are outdated/faulty, after "icon-click" it opens only menu, no validation at all...

Lacks an option to ignore certain error/warning types which is important since the official validator flags errors for non-standard attributes which are still VALID under HTML 5. Makes the results very hard to use for anyone using AngularJS or similar on their site.

Ian RenyardDeveloperFeb 8, 2017

This sounds like something that may be useful. I'd really appreciate it if you raise this as an issue at https://github.com/renyard/validity/issues with an example of some of the errors/warnings (and/or a URL/HTML snippet with the errors), please? I have looked into doing something similar in the past for individual messages, but maybe a blanket ignore on warnings might work? The issue in the past was around configuring and reliably identifying the messages to be ignored.

icon show in bar but did not work

Ian RenyardDeveloperFeb 8, 2017

After installation, you will need to reload any pages that you want to use Validity on. Extensions also do not work on the Web Store at all. These are both due to limitations of Chrome's extension API. If you're still having problems, I'd appreciate it if you could raise an issue at https://github.com/renyard/validity/issues and I'll investigate.

The only validation plugin that works for me for webpages that are not online yet / on a proxy. Works like a charm, thanks.