html5rules
Forum Replies Created
-
Forum: Themes and Templates
In reply to: HTML5 Lang Attribute problemsYes actually it was completely because of the W3 Total Cache plugin meaning there’s a bug or something there, more specifically it was the Minify feature causing this so I’m looking into it now.
Thanks for everyone’s help!
Forum: Themes and Templates
In reply to: HTML5 Lang Attribute problemsEric, it’s not the cache, I’ve tried that many times. If I were to remove the ‘lang’ attribute from the header and try the http://achecker.ca/checker/ validator again after flushing the cache you can see the change because then the ‘lang’ attribute isn’t there but the XML namespace still is.
<html xmlns=”http://www.w3.org/1999/xhtml”>
And I just tried that now so the cache is not the source of the problem, I even tried disabling the W3 plugin and turning it back on after.
Forum: Themes and Templates
In reply to: HTML5 Lang Attribute problems<!DOCTYPE html>
<html lang=”en”>
<head>You can see that I don’t really want the XML namespace there because it’s HTML5 and like I said, when you look at the source from http://achecker.ca/checker/ you can see how it’s changed my code and on the W3C validator the source is just as it should be.
Forum: Themes and Templates
In reply to: HTML5 Lang Attribute problemsThanks, I’ve reported this as a bug and tagged that it needs more documentation. On the support files it actually says we don’t need to know about XML namespace which I think is a bit biased if you’re a developer… Nevertheless, we’ll see what they have to say.
Forum: Themes and Templates
In reply to: HTML5 Lang Attribute problemsThanks for your reply, I am aware of this. I removed the XML namespace from within my code that was giving me the WCAG error. However, I noticed that using the above WAI validator, the XML namespace appeared in the code, and when I validate the HTML using W3Cs service, the XML namespace isn’t there like it should be. I then took that code and pasted it in the WAI validator which came out valid.
I think what WordPress does is add the XML namespace to certain user agents, I don’t know which ones but that seems to be the root of the problem and perhaps something the official team should have a look at when make the transition to HTML5 in the future as the namespace is only used in XHTML so it shouldn’t be there in the first place.
Well that’s managed to sort out the problem in a kind of way but definitely something that should be looked in to.