Fix !ComboBox memory leak on IE8 on page refresh:

1. Don't set dojo.store item as an expando property of the drop down list DOMNodes.   (DOMNodes pointing to javascript objects causes leaks.)

2. Avoid closure issues on aspect.after(widget, "destroy", ..) call by putting callback function outside of the function calling aspect.after().

3. Accessing !ComboBoxMenu.containerNode.childNodes was also leaky.   I guess it's asking for trouble returning a live collection from a function.

4. The registry._destroyAll() call doesn't seem to be necessary on page unload, even for IE6, so removing it for now.

Fixes #15206 !strict.
removed another unused ref to dojo/_base/window,  refs #15216 !strict
Make Destroyable mixin to track handles or other objects (including supporting widgets) owned by the instance, and to remove/destroy those objects when the instance is destroyed.

Also made _WidgetBase.destroy() automatically destroy all supporting widgets, without needing to register them via this._supportingWidgets[] or this.own(), unless they are special widgets that relocate themselves outside of this.domNode (i.e. popup widgets like Tooltip or Dialog).

Code partly from [28120], fixes #12429 !strict.
Fix double bubble of Button click event, and add tests, refs #13785 !strict.
Clarify ComboBox doc in light of recent store changes. Fixes #13380.
fix typo, thanks twk3, refs #11622 !strict
Convert dijit/tests/robot files to AMD, refs #14929 !strict
Support disabled tabs, fixes #5601 !strict.

Note that claro is the only theme that has a special grayed-out style for disabled tabs, and also for the disabled left/right arrow buttons (when the tabs are already scrolled all the way to the left/right).
Not sure if declare() requires a hash argument or not, but it confuses the doc parser if it isn't there.   Refs #13101 !strict.
Refs #13101. Separate code comment from docblock.
Refs #13101. Fix various dojodoc comment errors and other issues with comments that prevent correct parsing.

!strict due to existing invalid code.
Use simpler design to implement !TextBox browser specific code paths.

Colin fixed the doc parser to understand the old design (ie, a !TextBox base class and browser specific !TextBox subclasses), but this new design seems easier for the doc viewer, and  given browser-specific builds, I don't see that one design is better than the other.

Refs #13854 !strict
fixes #4763: modified various widgets to use dojo/mouse.wheel
Doc fixes.   Not that this file is *only* used by the doc parser.   Refs #13101 !strict
a few more doc fixes, refs #13101 !strict
Refs #15216: dijit.range.create() argument is optional until 2.0

fix broken backward compatibility
Fix problem on horizontally scrollable trees where blue (or orange) background for hovered and selected rows doesn't extend all the way to the right, in the case where the tree has a horizontal scrollbar because some rows are wider than the Tree itself.

I couldn't figure out a way to do this via CSS; it's complicated since some rows are narrower than the Tree (ie, narrower than the Tree's offsetWidth), whereas some are wider, and we want the background for both types of rows to stretch the correct distance.   So I added javascript sizing, done after any synchronous or asynchronous drawing operation completes: ex: expanding a single tree node, set("paths", ...), or collapseAll().   If the performance turns out to be unacceptable  may need to rethink the solution.   (The code is not optimal, but seems to perform well enough.)

I moved the indentation to a sub-node of the dijitTreeRow, and on claro, I removed the left and right borders.   Together, this makes the sizing easier: I can set this.rowNode.style.width directly rather than calling domGeometry.setMarginBox(this.rowNode, ...).    It seems like those left/right borders would be unwanted in general anyway, specifically when the Tree is inside a box such as the left-hand pane of a mail web-app, and thus there's already a left and right border flanking the tree.

Fixes #13141 !strict.
Test code was comparing a string to an array, and for some reason it worked until [27975], when it started failing on chrome windows.   (It should never have worked anywhere.)   Fixing it to compare string to string, refs #13785 tangentially.
Refs #13101. Fix bad docblock tag.
fix typos from [28401], thanks Sudoh-san, refs #15206 !strict.