Semantic HTML » sphinn http://semantichtml.org Semantic Markup and Practices Mon, 23 Aug 2010 12:43:29 +0000 en hourly 1 http://wordpress.org/?v=abc http://semantichtml.org http://semantichtml.org/wp-content/plugins/maxblogpress-favicon/icons/favicon-42.ico Semantic HTML Sphinn Is Invalid http://semantichtml.org/semantics/sphinn-is-invalid/ http://semantichtml.org/semantics/sphinn-is-invalid/#comments Thu, 13 Dec 2007 18:26:24 +0000 Martin http://semantichtml.org/semantics/sphinn-is-invalid/ Just when I thought I had hacked every plugin on this site to validate the entire span of pages, it seems that Sphinn’s “sphinn.com code” is invalid HTML markup. Not that the small icon that is generated next to each post is invalid code. Because if that was the case, I would simply rewrite it to pass W3C validation, like I’ve done to the others on this site. But the problem lies with the javascript function that is called from the plugin. That JS plugin is sitting on the sphinn servers – and it generates styles in the form of <style type="text/css"> – at the head of the iframe it creates.

You see, it basically builds out a new page, but does not create a DOCTYPE declaration. It may be argued that one is not needed, but for semantic correctness, yes it does need one.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon] ]]> http://semantichtml.org/semantics/sphinn-is-invalid/feed/ 0