Comments on: Gotcha of inline Document Ready function for JQuery

By: Carl

Carl — Wed, 02 Dec 2009 17:32:46 +0000

This is neither jQuery bug, browser bug, XML bug, or parsing bug. It is a DTD specification problem. Browsers are simply obeying the rules that the W3C provides when parsing HTML. Fully explained here: http://aspnetresources.com/blog/empty_vs_nonempty_html_tags.aspx

By: Danny117

Danny117 — Thu, 19 Feb 2009 16:49:57 +0000

Hi, Brett Thanks for visiting my website and for this tip. It would've saved me lots of time.

I reference jquery with the masterpage script manager. I have my ready functions near the bottom of the page. I've also been able to use mutliple readys. One in the master page and one on the content page.

FYI I've volunteered to present to the group in July on ASP.NET with jquery and ajaxcontroltoolkit.

See you next month.

By: Brett Veenstra

Brett Veenstra — Tue, 25 Nov 2008 11:59:52 +0000

@colleen: Thanks for your comment. I hope we’re only a few years away from being able to write valid XHTML and have it parse properly!

By: colleen

colleen — Tue, 25 Nov 2008 06:25:40 +0000

There is some other reason why I always use instead of

It had nothing to do with jQuery, which wasnt even involved in my test where I just made this rigit rule. I cant remember, it's just in my notes always use maybe it's exactly the same thing you got. Firebug would prolly clear it in less than 1 hr.

By: Continuous Integration Gotcha: NAnt empty elements | Journeyman to Master

Continuous Integration Gotcha: NAnt empty elements | Journeyman to Master — Fri, 31 Oct 2008 13:43:13 +0000

[...] once I cleaned up this empty element, it worked! Interesting how this yet another reason why XML is the bane of [...]