widget.parent = this; widget.addedTo(this, idx+1);    delete dojo.widget.manager.topWidgets[widget.widgetId]; }, 
widget.parent = this; widget.addedTo(this, idx+1);    delete dojo.widget.manager.topWidgets[widget.widgetId]; }, 
		registerChild: function(widget, insertionIndex){			// summary: record that given widget descends from me			// widget: Widget			//		the widget that is now a child			// insertionIndex: int			//		where in the children[] array to place it			// we need to insert the child at the right point in the parent's 			// 'children' array, based on the insertionIndex			widget.dojoInsertionIndex = insertionIndex;			var idx = -1;			for(var i=0; i<this.children.length; i++){				//This appears to fix an out of order issue in the case of mixed				//markup and programmatically added children.  Previously, if a child				//existed from markup, and another child was addChild()d without specifying				//any additional parameters, it would end up first in the list, when in fact				//it should be after.  I can't see cases where this would break things, but				//I could see no other obvious solution. -dustin				if (this.children[i].dojoInsertionIndex <= insertionIndex){					idx = i;				}			}			this.children.splice(idx+1, 0, widget);			widget.parent = this;			widget.addedTo(this, idx+1);						// If this widget was created programatically, then it was erroneously added			// to dojo.widget.manager.topWidgets.  Fix that here.			delete dojo.widget.manager.topWidgets[widget.widgetId];		},
6315	/local1/tlutelli/issta_data/temp/all_js/javascript/2007_temp/2007/6315/2f1d2cb699c9d9329e8b782b0463156e211cb0f6/struts_dojo.js.uncompressed.js/buggy/src/main/resources/org/apache/struts2/static/dojo/struts_dojo.js.uncompressed.js