Loading Profile...
ID scripts use uppercase tag names (invalid XHTML)
I reported reported multiple times over the past year for you to use lowercase tag names in your scripts (to make them work in XHTML). Every time I have been told that it will be fixed right away (to no avail). Please don't lie to me and say that you will fix something if you never plan on fixing it. Don't just tell me that you "will fix it soon". It would take almost no effort to replace "SCRIPT" with "script", etc. Only reply after you actually FIX this.
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hi Elijah,
Are you using the latest version of the plugin? I'm using it on my website, and as you can see, it validates as XHTML 1.0 Transitional: http://validator.w3.org/check?uri=htt...
I've been changing any references I see to lowercase as I go through the code, and I'm not currently aware of any that I've missed. I'd be happy to change any if I've missed some though.
Beau3 Comments
Add a comment
This solves the problem
-
I said ID scripts not ID script tags. For example in look at all of the document.createElement calls in from intensedebate.com/js/wordpressTemplateCommentWrapper2.php. Also, make sure to use .toLowerCase() when using nodeName (which is all-caps). This has nothing to do with the plugin, but with the ID service itself. -
I've just changed a *bunch* of these, but it's possible I've missed some. Let me know if you spot any others and I'll also keep an eye out for more as well.
I'm curious as to what (if any) problems these JavaScript-based tags have caused you, since they wouldn't be technically validated by any validation service I'm aware of? -
It's not the validity that I'm concerned about (an XHTML-compliant browser actually validates the XHTML and doesn't render the page if it's invalid), it's that there is no such thing as SCRIPT in application/xhtml+xml so document.createElement("SCRIPT") is the same thing as document.createElement("FOOBAR")
