Comments on: IE 6 bug causes jQuery globalEval error

By: Volomike

Volomike — Thu, 17 Dec 2009 01:38:55 +0000

This problem is occurring for me on IE8 with jQuery 1.3.2. It’s a bug in jQuery that rarely occurs and only with IE. In my particular case, I had an OBJECT with an EMBED inside in the page. My object had an ID of player, and my embed had an ID of player2. I then did this:

var s = $(‘#player2′).html();
$(‘#player2′).html(s);
s = $(‘#player’).html();
$(‘#player’).html(s);

And that’s when this line 12 error occurred.

By: Arthur McLean

Arthur McLean — Mon, 27 Apr 2009 18:32:14 +0000

This bug is back in jQuery 1.3.2.

By: Nik

Nik — Thu, 18 Dec 2008 14:19:45 +0000

Duncan, thanks so much for this.

By: name

name — Mon, 01 Sep 2008 01:32:03 +0000

Good day!,

By: krick

krick — Sun, 31 Aug 2008 03:30:57 +0000

Thank you for posting this. You’ve allowed me to fix a long-standing bug with my Joomla powered website and IE6.

This bug shows up in Joomla when you enable search engine friendly URLs. Enabling SEF causes it to emit a self-terminating BASE tag into the head of your page. If your Joomla template includes certain javascript files and they end up after the BASE tag, the bug shows up. In my case, it was this wowhead script…

http://www.wowhead.com/?powered

I made a post on how to fix it by editing one of the core Joomla files…

http://www.tankadin.com/latest/ie6-can-t-be-trusted.html

By: LG

LG — Sat, 07 Jun 2008 14:39:19 +0000

You rock!

By: JQuery Global Error With IE6 « Corey Kimball

JQuery Global Error With IE6 « Corey Kimball — Wed, 21 May 2008 19:14:48 +0000

[...] googled around a bit, and came up with this post, which fixed the [...]

By: Junaid Ali Qureshi

Junaid Ali Qureshi — Tue, 20 May 2008 14:06:47 +0000

Well jquery 1.2.3 also shows similar behaviour on IE6 and trust me i dont even use a base, i have tried alot of things but i still get the error.

By: Chris Venus

Chris Venus — Mon, 28 Apr 2008 17:13:38 +0000

I realised the other day a while after you said about this that the problem occurs probably because of the legacy of how IE originally implemented base.

It used to be that base wasn’t an attribute that applied to the page. It was markup that applied to the section it was enclosing. That meant that you could apply a different base element to different parts of the page.

http://blogs.msdn.com/ie/archive/2005/08/29/457667.aspx

That discusses it a bit more. Now *why* this caused the bug I don’t know but that must be why it was happening because it was trying to extend our base element to encompass a section rather than being standalone.

You may have known this already but I thought it was interesting context to add to the main article. And also an explanation and reassurance that they fixed it for IE7. :)

By: Srinivas Narayanan

Srinivas Narayanan — Fri, 25 Apr 2008 14:34:53 +0000

This post was a life saver for me. I was struggling with this for the entire day. And your post made all that worthwhile. Thanks a lot.

Cheers
Srini (nacnez)