The problem was fixed when I removed the SRC attribute from the iframe and I added onOpen event to jQuary's dialog.
The problem was fixed when I removed the SRC attribute from the iframe and I added onOpen event to jQuary's dialog: open: function() { document. GetElementById("mainFrame"). Src = "/login.
Aspx"; }.
Fancybox creates the iframe on the fly. I don't know how I could work this in to the process. – invertedSpear Aug 1 at 16:42 Thanks!
This seemed to solve my problem as well. – GregL Oct 27 at 4:26.
D'oh, thought I had the latest fancy box. Turns out I had 1.3.1, 1.3.4 fixes this issue.
I had the EXACT same issue, but the cause of mine was different. I figured I'd share here in case others were in the same boat as me - especially given that it took me about 4 hours to track down... Our main page had an iframe which ended up having its src attribute changed twice in a very short amount of time (we were actually loading the same src twice by accident - once directly in the HTML and then again on page load via JavaScript). I'm not sure why Internet Explorer 9 chokes, but I'm guessing that the frame was partially through initializing its scripts when the src was set again, putting the JavaScript engine into an unhappy state.
Either way I'm glad I found it, since we shouldn't have been loading the frame twice! However, the real reason why Internet Explorer 9 died so bad is a mystery.
I had the EXACT same issue, but the cause of mine was different. I figured I'd share here in case others were in the same boat as me - especially given that it took me about 4 hours to track down...
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.