Internet Explorer Cannot Open the Internet Site- Operation Aborted

By scientific method (or was it trial and error?) I also confirmed that it is the tabs helper module that causes IE to abort. IE7. Using 5.x-0.8.

The crash happened because of code within a JS script called jquery.history_remote.min.js

What this script does it's what would be called a "hack"... under IE it requires making changes to the page (adding an invisible IFRAME). Normally, when you dynamically make changes to a page you're advised to do it inside an "onload" handler... otherwise things might go wrong. In practice things don't normally go wrong... except when Flash is around in which case you might or might not have problems (the reason why is hidden along with IE's source code). The thing is, "onload" is an event called after the whole page (and images) are loaded and rendered... which is overkill, because it'd be enough to wait until the DOM is loaded, no need to wait for images. Firefox provides a "dom loaded" event, but IE doesn't.

... enter the JQuery library, used by Drupal (and by the guilty script in particular), which provides a hook for Firefox's "dom loaded" event, and attempts to simulate it under IE (I'm talking about the $.ready function).

The Fix is in jquery.history_remote.js which is loaded by the tabs code for the permalink urls.

I have attached the fixed script.

The D6 version of tabs doesn't have history. Yes, probably we should either remove it from D5 or else at least make it optional. I'd welcome a patch.

@klamping - not sure what you're asking? What do you want to make optional?

Here is what fixed the problem for me:

http://drupal.org/node/199524#comment-827965

Either use the altered jquery.history_remote.js (attached to that comment) or change the module and stop it from calling it altogether. The Drupal 6 version of the module doesn't use it anymore btw.

This bug really should be taken seriously by the maintainers of this module.

This bug really should be taken seriously by the maintainers of this module.

I haven't reproduced the issue and so cannot fully test. Comment #3 reported that the patch broke tabs.

I'd welcome a patch with reviews.

The error happens when you combine this script with for instance reCAPTCHA or swfobject.js. You should be able to reproduce it when you enter one of those objects in your page.

Budda,

Your script fixes the "cannot open" error but it effectively breaks tabs. Do you know what else needs to be changed in order to get them working again?

I can confirm this bug for 5.x-1.1 as well.

For better understanding I created a patch for #2's solution (patch for 0.8). All we need now is a way to figure out how to get tabs working again with this patch applied.

So, in summary:
- no crash anymore when you use $(window).load instead of just $() (which is a synonym for $.ready), which caused it the history plugin to be loaded too early in IE6, in turn causing weird problems when combined with Flash on the same page
- the history is now being loaded later, but the tabs plugin isn't, which somehow causes it to fail. So we need to make sure the tabs plugin only loads *after* the history plugin has loaded.

How about:
- add an id attribute to the iframe that's being added by the history plugin
- don't load the tabs plugin until the aforementioned id is found

Seems the least hacky approach?

So, I'm confused -- as I don't have a jsquery.history_remote.js -- I haae jsquery.history_remote.pack.js, which doesn't look anything like the patch. What am I missing?

Nick, the patch is for version 0.8 (which uses history_remove.js), not for version 1.1 (which uses history_remote.pack.js).

After more testing, it looks like my patch for #13 by itself fixes this issue without breaking tabs. It would be great if someone could confirm this.

I have the 1.1 version of jstools, so the above mentioned patch wasn't of much use. What did work for me was commenting out line 160 in tabs.module:
drupal_get_path('module', 'jstools') . '/jquery.history_remote.pack.js',

So far I haven't seen any side effects. Those parts of the site that use tabs work just like they did before and the error message is gone..

I made the history remote plugin optional, defaulting to disabled.

Thanks so much for this Nedjo!