Videos
We are seeing file errors on upload for the first time ever since it was announced at least a year ago that the tool was being deprecated (I never understood why Google doesn't like it, except they want revenue).
Seeing as this tool is no longer maintained, could this be the end of the free H5 vaildator for AdOps and Creators? Are there other free HTML5 validators out there that work as good?
Google DCM HTML5 Validator will be deprecated without a replacement March '21..
Our studio relies on this to make sure creatives will not be rejected when uploaded to DCM. Anyone know of any alternatives? Thanks!
EDIT: Nevermind! deprecation postponed, thanks to anyone who raised concerns..
Google is baking it in to cm on the advertising side and bet they will have something similar on the studio side. It was supposed to roll out end of last year I’ll see if I can find an update.
What the fuuuxck ...
Edit: possible they are porting this over to the platforms instead of being stand alone but still checking
HTTP Error 500 is an Internal Server Error, so that will be their fault. Try validator.nu whilst you are waiting.
W3C validator maintainer here. Tip: Next time you see that message, try validating your document directly at http://validator.w3.org/nu/ instead.
Because if you see that 500 error it means the validator is trying to reach the HTML5 backend, which runs as a separate service/process responding at localhost:8888 on the validator host.
But we actually run several validator hosts, round-robin, so if you see that 500 error it could mean that only one of the HTML5 backends on one of the hosts is temporarily down. And if you go to http://validator.w3.org/nu/ you might get lucky and hit a different host and it'll work.
On the other hand if you get a 404 from http://validator.w3.org/nu/ it most likely means you caught me in the middle of restarting/redeploying the W3C HTML5 validator backends to pull in changes I've made to the sources from https://github.com/validator/validator
But that never takes me more than a few minutes, so on your end you should never be seeing that 500 error for more than, say, 10 minutes at most. So if/when you do see it for any longer than that, please report it either by tweeting to @w3c or @sideshowbarker on twitter, or pinging me on IRC (MikeSmith on #whatwg or #w3c on irc.freenode.net).