okt 6 2014 20:20 Barney Carroll <barney.carr...@gmail.com>: > So 'validate your markup', as much as it may be good advice, wouldn't have > caught this particular fish. In fact, I might assert that 'validate your > markup' hasn't taught us anything with regards to this particular problem. > The reason people come to this list is usually to seek human insight and > communal effort on given problems, which code parsers are unable to give. > Conversely, actually reading about Bob's problem, visiting the URL and > trying to replicate the behaviour he described proved to be a really good > first step to solving the problem.
Good catch of a javascript error on a css list. However, none of what you mention concern even one reasonable reason not to validate your HTML and CSS code. For nothing else the chances increases to get that help you think you need. Even it wasn’t a css or HTML issue this time, too many times it is the invalid code or stupid little mistakes. And even if it isn’t, there are other issues because of it. Not too seldom I encounter company web sites that contain bugs with invalid code so serious that it’s embarrassing to point out the mistakes that took me 2 minutes at worst in a validator to find, 2 more minutes to correct. Obviously I find the developers of those web sites unprofessional. Invalid code? It’s not the end goal, but a nice and useful stop on the path I choose to take. so, Nah! ______________________________________________________________________ css-discuss [css-d@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
