Nice fix! Sorry you had to hack around our problem. If it's any consolation I think this is fixed for others as of today by replacing
window.location = '#idc-container';
with
window.location.hash = '#idc-container';
Which should already by live.

If you'd prefer not to poll to check when IntenseDebate loads, we offer some JavaScript hooks to detect that via our plugin system. There's more info here: http://www.intensedebate.com/docs/plugin-resource... but the basic idea is that you can register a JS function that we will fire on certain events (including IntenseDebate loading). Might be a slightly nicer solution if you're interested in poking around.

Again, sorry for the trouble, but nice job working around it!

The update should appear on your WP plugins page now. If for some reason it's not, you can always download it from here: http://wordpress.org/extend/plugins/intensedebate

Yes this is true. My main concern with 3rd party scripts is that the end of the first script might not be the end of the necessary JS. Often remote scripts will then load multiple other objects/scripts that may be necessary for the code to function properly. And since it's a remote script, even if this isn't the case today, it could be tomorrow ;-) It's a safe bet if it's your own JS though that you know when the last bit of JS you need is and can insert it there. You can even include it as a conditional paramater in the script request if you don't want it to load all the time. Like:
http://mydomain.com/js/script.js?callback=true

Or something similar, which can then be setup to only include the function call when that parameter is set.

Interesting technique. I've not seen this queuing method before, but I have seen another method of dealing w/ this problem that is very similar. Basically, the idea is that when you load the javascript links initially you give them dummy functions that queue the function call, but then replace the href once the javascript is loaded (and execute the queue). It avoids the wrapper but at a rather expensive replacement of the links. I think your idea of a wrapper function is a bit cleaner, but generally eval is pretty bad with large functions/bodies of code in my experience, so the other technique may work better if it's any more complicated than a straight function call.

One thing you might consider to get a slight bit of extra performance is adding the dequeue_actions(); call to the end of the javascript you're loading (assuming you control the script and it's not loaded from a third party). This will allow the js to execute as soon as the necessary javascript is loaded instead of waiting for the onload event (which on a heavy page could be noticeably later).

Give IntenseDebate a try!

Very exciting

Yet "another" reply. I'm so glad

another "reply" I'm happy to say

You really \"think\" so? I\'m really happy.

You should now be able to add it from your blog's settings page at IntenseDebate.com.