Comments on: Don’t believe everything the Validator tells you http://www.webdevout.net/tidings/2008/06/22/dont-believe-everything-the-validator-tells-you/ Updates on the march of progress. A weblog about web design, standards, web browsers, and the overall health of the Web. Wed, 14 Dec 2011 14:45:24 +0000 http://wordpress.org/?v=2.8.4 hourly 1 By: Flüge http://www.webdevout.net/tidings/2008/06/22/dont-believe-everything-the-validator-tells-you/comment-page-1/#comment-4127 Flüge Wed, 12 Nov 2008 12:42:53 +0000 http://www.webdevout.net/tidings/2008/06/22/dont-believe-everything-the-validator-tells-you/#comment-4127 I always kept something like this in mind, now I know it's true. Thanks for the examples. I always kept something like this in mind, now I know it’s true. Thanks for the examples.

Posted using Mozilla Firefox 3.0.3 on Windows.

]]> By: Mitch 74 http://www.webdevout.net/tidings/2008/06/22/dont-believe-everything-the-validator-tells-you/comment-page-1/#comment-4098 Mitch 74 Mon, 23 Jun 2008 12:50:35 +0000 http://www.webdevout.net/tidings/2008/06/22/dont-believe-everything-the-validator-tells-you/#comment-4098 To be fair, the two latest examples can be detected by Firefox (at least) switching off Strict mode into Quirks mode. About the id =/= name, due to inconsistencies in both the specs and UAs, it's best to always duplicate id and name where relevant/possible anyway. The attributes types could be justified this way: currently decimals are used, what happens the day we switch to another system? Say, one where zones appear on a different media - like, say, "brainreader-wavelength 900"? Or, more realistically, "BraillePanel:20" For the unstackable stacked nodes though, well, this kind of mistakes hints at an error in the CMS - or PEBCAK. To be fair, the two latest examples can be detected by Firefox (at least) switching off Strict mode into Quirks mode.
About the id =/= name, due to inconsistencies in both the specs and UAs, it’s best to always duplicate id and name where relevant/possible anyway.
The attributes types could be justified this way: currently decimals are used, what happens the day we switch to another system? Say, one where zones appear on a different media – like, say, “brainreader-wavelength 900″? Or, more realistically, “BraillePanel:20″

For the unstackable stacked nodes though, well, this kind of mistakes hints at an error in the CMS – or PEBCAK.

Posted using Mozilla Firefox 3.0 on Linux.

]]>