Critiques pour Html Validator
Html Validator par Marc Gueury
5 notes
- Noté 3 sur 5par Lantana Al, il y a 2 ansSadly does not support CSS HTML Validator any longer... but maybe Marc will one day be able to add support for it back in.
- Noté 3 sur 5par Utilisateur ou utilisatrice 17605223 de Firefox, il y a 3 ans
- Noté 3 sur 5par vee, il y a 3 ansOffline validation cause some false warning. For example, this code `<button class="btn btn-outline-secondary" type="submit">ค้นหา</button>` cause "Warning: missing </button>". Use W3c online return correct result.
- Noté 3 sur 5par Utilisateur ou utilisatrice 12760379 de Firefox, il y a 6 ansFirst you have to open the DevTools and click on the Validator. This is one more click than before. And you can't see immediately that there are problems while surfing, because the icon is always grey in the toolbar. This is unfortunately a step backwards, therefore only 3 stars instead of 5 as before.
- Noté 3 sur 5par Alessandro, il y a 7 ansWith FF 60 still sees the source generated by browser instead source generated by server. The Options of this extension are partial broken... not able to select GSML, always gets TIDY... partial working on FF 60, needs to be reworked again to be useful under FF 60 and more...
EDIT: in chrome this extension don't work anymore... won't validate my web pages, instead to see a green flag I can see only a message "Info 0 0 No HTML" and nothing other... the flag remains gray...
This happens on latest version of Chrome! Version 66.0.3359.181...Réponse du développeur
mis en ligne : il y a 7 ansThe exact same HTML Validator extension/code works fine in Chrome. The reason being several bugs and mostly one API not implemented in FF.
This is the chrome version (in fact the same file): https://chrome.google.com/webstore/detail/html-validator/mpbelhhnfhfjnaehkcnnaknldmnocglk
For more explanation, please look in the bugs below.
https://github.com/mgueury/html_validator/issues/11
https://bugzilla.mozilla.org/show_bug.cgi?id=1361121
and mostly vote for the FF bug to be fixed :-)
Thanks,