search

thomasdavis / w3cjs

A npm package for testing files or url's again the wc3 validator
http://thomasdavis.github.com/w3cjs/
The Unlicense
159 stars 25 forks source link

Updated to use validator.w3.org/nu/ #19

Closed swillner closed 9 years ago

swillner commented 9 years ago

Unfortunately I didn't find anything on how to use the doctype and encoding option in the new validator interface

swillner commented 9 years ago

fixes thomasdavis/w3cjs#17

callumacrae commented 9 years ago

Looks good to me! Would be good if we could get the doctype and encoding options back, though.

swillner commented 9 years ago

The options don't seem to be available anymore, also the "official" W3C-checker does not support them: http://validator.github.io/validator/ The encoding seems to be auto-detected, but could be provided in the HTTP header (Content-type). A workaround for the doctype could be simply prepending the document with a "<!doctype ...>"

thomasdavis commented 9 years ago

Anyone know which semver I should bump this to?

callumacrae commented 9 years ago

Depends if the output has changed. If the output changed, major, otherwise minor.

My guess is that it's a minor release—the tests didn't need changing which suggests the output is the same.

callumacrae commented 9 years ago

I'm now getting this from gulp-w3cjs:

[15:44:49] HTML Warning: valid.html Line undefined, Column undefined: The Content-Type was “text/html”. Using the HTML parser.
[15:44:49] HTML Warning: valid.html Line undefined, Column undefined: Using the schema for HTML with SVG 1.1, MathML 3.0, RDFa 1.1, and ITS 2.0 support.

I didn't get that before. Any ideas how I can get it to go away?

swillner commented 9 years ago

That is going to be hidden by default when separating info messages (like these) callumacrae/gulp-w3cjs/pull/11