>His version will probably fix some of the issues i am encountering with my
>little hack (which works, but not very fault-tolerant) ...
Not necessarily :-)

I just checked in a enhanced ContentPane in under layout project in Dojox.
You all know that dojox is a extenal tree from dojo and dijit, open for more experimental stuff.
It includes executeScripts, among other things.

changes from 0.4 (some names might be badly chosen, please help in finding logical ones)
scriptScope -> gone
scriptSeparation -> gone, always in global
executeScripts -> default true
adjustPaths -> default false

new:
cleanContent -> default false
        removes tags that is likely the throw DOM or JS errors, <DOCTYPE ..>,
        <title> and html comments <!-- *JS code* //-->,
        <![CDATA[ *JS code*]]> from JS.

renderStyles -> default false
        snarfs <style>*cssText*</style> tags and <link rel='stylesheet' href='..'>
        and inserts those into document head.
        ensures that it works X browser, innerHTML <style> actually throws in old
        Opera's or was it old Khtml, any way innerHTML a <style> tag doesn't do a
        thing in other browsers

ioArgs -> default {}
        ioArgs to xhrGet,
        example:
        pane1.ioArgs.headers ={
                'X-myOwnHeader': 'yepp it works!',
                'X-getMePage': 2
        };
        pane1.refresh();

ioMethod -> default dojo.xhrGet
        ioMethod used to download data
        example:
        pane1.ioArgs.content = {page:2};
        pane1.ioMethod = dojo.xhrPost;
        pane1.refresh();

scriptHasHooks -> default false, Bad name?
        The keyword _container_ in your JS code
        is replaced before eval with dijit.byId('this.id')
        example of form handler (could of course go into onLoad just as easily):
       <div dojoType='dojox.layout.ContentPane'
                scriptHasHooks='true'
                ioMethod='dojo.xhrPost'
                href='myFormPage'
       ></div>

       myFormPage:
        <script>
             _container_.onLoadDeferred.addCallback(function(){
                   var form = dojo.query('>form', _container_.domNode)[0];
                   var conn = dojo.connect(form, 'onsubmit', null, function(evt){
                         dojo.disconnect(form); dojo.stopEvent(evt);
                         _container_.ioArgs.form = form;
                         _container_.refresh();
                   });
            });
       </script>
       <form>
          <input name='value1'/>
          <input name='value2'/>
          <input type='submit'/>
       </form>

new methods:
onLoadDeferred  is a dojo.Deferred
        callback on onLoad, if isLoaded = true fires immediately

onUnloadDeferred is a dojo.Deferred
        callback on onUnload

onExecError, event
        script download, but doesn't fire on parse or runtime error, havent figured
        out why yet

setHref(), refresh() and setContent() returns a handle
        handle = {
                cancel()
                addOnLoad(func)
                addOnUnload(func)
        }

        example:
        pane1.ioMethod = dojo.xhrPost;
        var handle = pane1.setHref('getform');
        handle.addOnLoad(function(){
                var ev = dojo.connect(dojo.byId('myForm'), 'onsubmit', null, function(e){
                        dojo.stopEvent(e);
                        dojo.disconnect(ev);
                        pane1.ioArgs.form = dojo.byId('myForm');
                        pane1.refresh(); // we should set up handle here again,
                                                 // but you get the idea
                });
        });

It is also possible to use a <table>,<thead|tbody>,<tr> as a DOM node (they
are readonly to innerHTML in IE)
Content must still be valid though, if domNode is <table> your content must be
"<tbody><tr><td>*new content*</td></tr></tbody>"

It just works as expected in IE just as in FF.

So go ahead and test it and comment on errors, brainslips, hard to understand features, namechanges etc.

/ Fredrik