I’ve heard of other problems with that other approach too, but never confirmed them. But the opportunity just arose: I’ve started working on an Adobe AIR version of the script that uses the queue approach above, but AIR prevents the use of eval() for security reasons. Should be interesting to see if the DOM approach works instead…!

- Ben

As for your “better solution” there are some cases that the domscripting example does not apply.
For example.

My application generates a report that has quite a few output tables with hundreds of rows with tens of cells fancy sorting, etc, etc.

This can cause real heartache with IE trying to render all those tables at the same time.

My solution was to write those tables to hidden the value of hidden fields and then sequentially load div’s with the table code.

This allows IE to focus on one table at a time and keeps it from crashing under the load.

Your g_queue solution worked perfectly and I am a very happy man.

thanks again
-Scott

http://domscripting.com/blog/display/99