Fix #867: List: Don't call inherited destroy if useTouchScroll is false
CHANGES.md: Note useTouchScroll: false + destroy fix
Use direct DOM sibling accessors to get previous and next rows to avoid catching parent or child tree nodes in overlaps
Test stores: Make async country store observable to test tree edits
tree: Add unit test for child modification
CHANGES.md: Note tree child modification fix
tree unit test: Uncomment afterEach now that the test is verified
Fix #757: Selection: Listen for both touch and mouse/keyboard events

This revises event listener initialization logic to hook up both touch
and mouse/keyboard event listeners on webkit touch devices.  A flag is
set when a touch event is triggered, to avoid re-triggering Selection
events on emulated mouse events.
ColumnSet: Remove has("touch") conditions for touch+mouse devices
List: Default useTouchScroll false on platforms w/ visible scrollbars

This disables the TouchScroll module's behavior on platforms where
has("touch") reports true, but discrete scrollbars are rendered.

This is an admittedly somewhat loose heuristic, but achieves in
preventing TouchScroll from hindering on platforms that typically
have mouse input available, such as IE and Chrome on hybrid Windows 8
laptop/tablet devices.  These platforms generally do just fine with
native touch scrolling support, as well.

Unfortunately, there is no known foolproof solution to feature-detect
the presence or absence of a mouse.
DnD and util/touch: Tolerate mouse events on touch-supported devices
CHANGES.md: Note fixes for mouse+touch devices
Minor functional test code cleanup
Fix #775: Fix has-css3 feature detection, especially css-transforms3d

css-transforms3d was testing using a media query which is not supported by
non-webkit browsers.  Testing using the `perspective` style property is
sufficient in all but now-ancient versions of Chrome.
CHANGES.md: Note has-css3 fixes
Add warning about not setting sort on observable stores
Test cleanup, primariy adding sort property where missing
Minor test fixes
Fix #876: editor: Reference correct column during change handling

editor sets up a single delegated event handler for native input elements,
but it was always referencing the first column that it happened to set up
the handler for.  This happened to be mostly harmless in most cases, but
caused issues particular to radio button handling.
CHANGES.md: Note editor input change event handling fix