Frameset Bug in Internet Explorer
Imagine the saddest you've ever felt; that's what the last 12 hours of my work life have been like. I've spent most of the last two days investigating a situation in which closing the browser window would cause IE to continuously spawn new windows. Since we're dealing with a "Web 2.0" application containing thousands of lines of Javascript, the first instinct is to scrub the code for
Instead, I've discovered a bizarre bug in the way IE handles framesets. Turns out, if a frameset frame contains a url containing an anchor, and the browser is closed before that particular frame has completed downloading, IE will begin endlessly spawning new windows.
The lesson?, avoid anything looking like this:
window.open(). But that revealed nothing.Instead, I've discovered a bizarre bug in the way IE handles framesets. Turns out, if a frameset frame contains a url containing an anchor, and the browser is closed before that particular frame has completed downloading, IE will begin endlessly spawning new windows.
The lesson?, avoid anything looking like this:
<frameset>
<frame src="somepage.aspx#anchor"></frame>
</frameset>