Skip to main content

Bug Tracker

Side navigation

#1187 closed bug (fixed)

Opened May 14, 2007 04:26PM UTC

Closed June 21, 2007 07:23PM UTC

IE: removing of #__ie_init in a FRAMESET causes weird loading of another frame (SVN)

Reported by: blueyed Owned by: brandon
Priority: major Milestone: 1.1.3
Component: event Version: 1.1.2
Keywords: Cc:
Blocked by: Blocking:

I've experienced the following problem using jQuery SVN and Internet Explorer 6.

If you have a frameset with two frames, the back/forward buttons behave weird: they cause a page to get loaded in a frame which does not belong there (and was not displayed there, before going to another link and pressing back).

I will attach files for testing this:

1. Extract the attachment to a directory

2. Put jquery.js into the directory (or adjust the path(s))

3. Open frameset_1.html in Internet Explorer

4. Click on "2" in the top frame

5. This will open frameset_2.html

6. Click "Back"

7. You will see "frame_b_2.html" in the top frame, instead of frame_a.html

This is caused by the following jQuery code:

jQuery(window).load(function(){ jQuery("#__ie_init").remove(); });

which was added because of ticket #1061.

My hacky solution for this was adding

if( ! window.frames.length )

before it, so that the code won't get used for FRAMESETs.

The real fix probably is to not include jQuery in a FRAMESET page at all, but if it gets done it should not cause this weird behaviour.

Attachments (1)
Change History (5)

Changed May 14, 2007 04:30PM UTC by blueyed comment:1

Like already mentioned in #1061, it would maybe be the best option to just always leave the __ie_init-Hack-Script in the DOM, wouldn't it? At least it has caused two different problems until now.

Changed May 14, 2007 08:11PM UTC by john comment:2

component: coreevent
need: ReviewPatch
owner: johnbrandon

I bet this could be fixed by doing jQuery(self) instead of jQuery(window).

Changed May 15, 2007 10:12AM UTC by blueyed comment:3

No, unfortunately not. At least not for the provided testcase.

Changed May 15, 2007 01:01PM UTC by brandon comment:4

Other than not cleaning up what are the problems (if any) of leaving the script tag in the DOM?

Changed June 21, 2007 07:23PM UTC by brandon comment:5

resolution: → fixed
status: newclosed

Fixed in Rev [2136].