I tried both under IE6

The if (document.all) clause in #2 makes sure IE will run the same commands in both. So no surprise they behave identical.

I only see the XP nodelet and the top of the freenodelet

See my remark in the middle of the post ("shortcoming"). Freenodelet has to be your bottom nodelet to not loose other nodelets below it.

Maybe that problem can be eliminated by having the script called from onload.

See my remark in the middle of the post ("shortcoming"). Freenodelet has to be your bottom nodelet to not loose other nodelets below it.

Duh (slaps head)!! Does that mean nothing else can be in the freenodelet as well? I put several links in there as I do not like the layout contraints in the personal nodelet. Regardless, thanks for the IE tweak!!

O. K., here is a fix, by separating definition of the function from its (then asynchronous) call.

All precious freenodelet content should stay intact. Also freenodlet can be any node in the series here.

<script type="text/javascript">
var doit = window.setInterval("FreeLeft()", 500);
function FreeLeft() {
    window.clearInterval(doit);
    var td = document.getElementById('nodelet_container').parentNode;
    var tr = td.parentNode;
    if (document.all) { // IE
        tr.insertBefore( td.cloneNode(true), tr.firstChild );
        td.style.display= "none";
    } else {  // w3c
        tr.insertBefore( td, tr.firstChild );
    }
}
</script>
[download]