This is our blog. It's mainly about programming, web developement and design, social web, coding habits and advice and miscellaneous geekery. You can subscribe to the feeds to never miss a bit.
Be Valid or die Learning (note to self)
So the bivalidator was launched in a hurry, and was appreciated by the people who tested it. Many have - of course- submitted the bivalidator itself to validation. The markup was fine, but the css didn't passed the validation due to this unclear fault that was returned by the W3C:
Servlet has thrown exception:javax.servlet.ServletException: Timed out
Some people noticed that and they were right to yell: "hey! your validator itself doesn't validate!" Well... the bivalidator just returned what the w3c CSS validator responded, but, yes, after all why didn't it validate?
After about 15 minutes of search and debugging, the answer was here: It doesn't validate because we put some css expressions in that style sheet to make the website run smoothly on IE. And that's it: The css validator is tourmented by these css expressions. It's its right: css expressions are not standards. And IE ought handle position:fixed rather than provide obscure features.
What a shame! We corrected this and made these "dirty" css hacks in a separate stylesheet that is available throught css condtionnal comments only to IE browers.
Now, the website validates :)
Enjoyed this post? please subscribe to our feeds to stay informed.
Commenting is closed for this article.
« Previous post: Here we go!
Next post: »
htmlSQL: a charming idea