When custom attributes conflict with validation

When custom attributes conflict with validation

Aug 08

I must confess, I am not a validation freak. Semantics and pixel perfection are my primary goals. Forgetting to specify a “type” on a javascript is not the biggest crime.

However I went ahead and validated the page I made for this telecom major. A social media campaign microsite which we created in five using restful calls and jquery in the front.

Back to validation, 11 validation errors awaited me, apart from the missing “type” attributes, I had custom attributes, ouch!

I was using those attributes among others for parameters, Ajax url’s. I knew the solution was a custom DTD, I remembered from a previous oroject where we had used adobe spry widgets, the software would drop a custom namespace on top of the header. Searching on the adobe site I figured that they had a tough time too and suggested having a entity tag in the header for the valufator and remove it when going to production.

Code samples in my case are in the next post.

Oh and other than that I had a custom live chat code that had reserved keywords and unescaped characters.

So what did I do? read my next post for the answer.