JQuery broken in IE7 & IE9 only?

Surprisingly, this seems to have been the issue. Somewhere along the line, the IE7 problem went away, but the IE9 issue persisted. When I changed the jquery from 1.5.0 to 1.5.2, the IE9 issue went away.

BTW: To those of you asking, the javascript as a whole was broken. Nothing worked. But this seemed to fix it!

Thanks! – Dan Cormier Apr 20 at 18:27.

(The prospect of booting up a Windows VM and IE to look for myself is not exactly appealing) A guess: A lot of times IE7/IE8 seems to be very picky about JSON notation. E.g. , if you end an object literal with a , it bugs out.

{foo1: 'bar', foo2: 'baz',} // General advice: Try using the DebugBar to debug problems in IE. It's certainly no FireBug but its the best you can get for free for IE debugging.

1 IE is fine with quoted object keys – Phil Apr 19 at 23:08 Thanks for the tip @chris. – Dan Cormier Apr 20 at 18:33 I've run into the 'trailing comma' issue before. It took me a while to figure out what was wrong.

– Sonny May 23 at 17:08.

I don't know about jQuery and IE per se, but I did have to tango with fancybox a while back with IE 7. I kept getting UI layout errors related to the IFRAMEs that fancybox were throwing out. If this sounds like what you're getting, I posted a blog post on a workaround I did at that time if you're interested in looking at it.

Thanks for the suggestion @richardneililagan. Fancybox wasn't the issue this time. Updating jquery from 1.5.0 to 1.5.2 fixed it.

– Dan Cormier Apr 20 at 18:32.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.