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. Fri, 21 Nov 2008 21:46:36 +0000 http://wordpress.org/?v=2.0.1 by: Mitch 74 http://www.webdevout.net/tidings/2008/06/22/dont-believe-everything-the-validator-tells-you/#comment-4098 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 (Not Specified) .

]]>