27 May 2004
Warnings and errors
MovableType doesn't produce valid HTML.
I suspected it as I was slowly modifying my templates, but I finally ran it through the validator and was attacked by tiny, unpaired, angle-bracketed fists of fury. Sure, they're probably cascaded from one or two errors early on, but how can you tell by looking at a page with 100s of errors?
But with even Google failing validation, is it hopeless? Should we just accept the chaos?
I was also somewhat surprised that they don't fix my entries. I can add random ampersands and angled brackets, and MovableType leaves them as they are instead of converting them to their approved W3C escape sequences. The biggest problem is ampersands in URLs. Why can't they parse my entry and replace those things?
A Web-savvy startup should be more attentive to Web-standards etiquette. I'm writing my congressman.
- Techniques after using Swift for a month posted by sstrader on 26 August 2015 at 11:41:51 PM
- Some thoughts on Ruby after finishing a week (minus one day) of training posted by sstrader on 15 December 2011 at 8:59:30 PM
- Links on the singleton pattern posted by sstrader on 9 December 2011 at 9:19:50 AM
- Phonebot posted by sstrader on 29 October 2011 at 6:37:05 PM
- The labeled break in Java posted by sstrader on 4 September 2011 at 11:27:56 AM