Do you train Kung Fu?
Or know someone who does?
Then check out KungFuPeople.com
Mobile version of this pageOne thing I hate about Linux: cron
Next:
pwdf - a mix of ls and pwd
Related blogs
Are you a web developer? Then VisiBone is for youparentElementsByTagName(doc, tagname, classname)
V8 < TraceMonkey < SquirrelFish
RememberYourFriends.com running jQuery
JetBlue a good and bad website
jQuery and Highslide JS
Why Django and Grok matters
To $('#foo p') or to $('p', $('#foo'))
In jQuery, using the :visible selector can be dangerous
Why I gave up on JQuery UI's autocomplete
QUnit testing my jQuery Mobile site in full swing
Related by category
JavaScript
Lesson learnt with creating DOM element with jQuery
3rd of April 2008
This took me some seriously wasted time to figure out yesterday. What I was trying to do was to create a DOM element of tag type A and insert it into the DOM tree of my page. As I was coding along, everything was working just fine in Firefox but the damn thing wouldn't show up anywhere in IE 6. I debugged and debugged and tried all kinds of different approaches and I just couldn't work it out. Then Karl Rudd gave the right hint on the jQuery mailing list.
Basically, what I was doing was something like this:
$('#toolbar').append(a);
What was then so strange is now less surprising. When I changed the <a> to a <span> it actually worked but just looked wrong with the rest of the site I was working on. Here's the correct way of doing it:
$('#toolbar').append(a);
Notice the difference between <a> and <a></a>. The strange thing is that to reproduce this I created this test.html page but here I noticed that in IE 6 it won't let you add any elements that are enclosing ones that are written as singulars. That's really strange since in the same javascript as the above stuff I did a $("<div>") which was working fine. I'll have to get back to figuring out why that one worked nad the A one didn't.
Comment
My guess why "<div>" worked and "<a>" didn't is that "div" tags can be nested, while "a" tags cannot; while each browser may have auto-closed the tags somewhere, IE didn't like the nesting.
btw whats the thought behind hiding captcha until user tried to add a comment... :S its annoying. i'm using google chrome
How the hell did I never know this until now? I've been coding with jQuery for almost a year now and didn't realize this until trying to debug an IE issue just this week. Thanks for the clarification.