non-zero insertIndex in programmatic TabContainer.addChild()

[gizmojo.org]

FF2.0, W2k, Dojo rev 10182.

Doing addChild() on a programmatically created TabContainer? (but used an existing div element as target) starting the insertIndex count from 1 seems to work just fine.

However, doing the same on a programmatically created TabContainer? that uses a dynamically created div element as target, then starting the insertIndex from 1 gives a ref has no properties error.

A test file (plus some more description) to reproduce the problem is at: http://dojotoolkit.org/forum/dijit-dijit-0-9/dijit-support/non-zero-insertindex-programmatic-tabcontainer-addchild

[Adam Peller]

insert at nth widget, not nth dom node

[Adam Peller]

I think the test case should fail, but it should fail consistently. Inserting at position 1 when there is nothing at position 0 should result in an exception. The reason it succeeds the first time is because the unnormalized DOM has empty text nodes.

Container.addChild should be adding based on the # position of widgets, not nodes. I'm attaching a patch, but I need to work up a better test to make sure it's right.

[bill]

Cool, looks good (well I haven't tried it but it look good), except that I think the query should be "> [widgetid]" not just "[widgetid]" since you only want to find children, not all descendants. See getChildren() function for an example.

[Adam Peller]

(In [10715]) Fix addChild insertion into _Container and StackContainer? specifying index. Fixes #4177