Clean up the scrollList after each test in KeyNavigator spec
Begin refactor of ScrollBarSpec
Complete refactor of ScrollBar tests
Derfault the y-axis scroll mode to slow, for flow and peek.  But, set to stop for single.
Fix Item Position Reported When Not In `flow` Mode

If the ScrollList is disabled during an interaction (between touch and
release events), the event positions reported are no longer relative
to the origin of its viewport, but are relative to the page origin
in the browser window. Currently the AwesomeMap will automatically
handle this in all cases.

For ScrollLists with nested AwesomeMaps for items, this correction
breaks down. The original event is handled first by the AwesomeMap for
the list itself, has its position normalized, and then is propogated
to the current item map, where a second normalization occurs. This
second normalization throws off the event position.
Re-Enable xit-ed Spec
Let us use a ternary....

…so that the default and override are not separated
Change AwesomeMap's normalizeEventPosition Option to `true`
Re-instantiate the ScrollList for each test
Merge pull request #53 from WebFilings/HY-1060_stop_at_boundaries_in_single_mode

Fix for Single mode in ScrollList -  Make it stop at boundaries.
Fix Misspellings and Refactor Test
Merge pull request #52 from WebFilings/fix_item_position_reported_when_not_in_flow_mode

Fix Item Position Reported When Not In `flow` Mode
Release 0.7.8
Merge pull request #54 from WebFilings/release_0.7.8

Release 0.7.8
Ensure that the scrollbar is placed before asserting it's position
Add a keyNavigator.dispose method
Merge pull request #51 from WebFilings/HY-1053

Fix Bad Tests in UIComponents
Keep Hit Area when Disabling AwesomeMap

Consumers want to have events flow to subscribers, but also
want to prevent any interaction from transforming the map.
Remove Stray Commented Code
Merge pull request #55 from WebFilings/keep_hit_area_on_disable

Keep Hit Area when Disabling AwesomeMap