Correct demo beacuse of exception
Update doc on registerRowBuilder
Fix #1955 (expandable): Left panel features coexistance
include header,footer,scrollbar when calculating initial grid height
scrollbars can be enabled per instance (horizontal or vertical)
and have the options: NEVER,ALWAYS,WHEN_NEEDED those er in
uiGridConstants.scrollbars.XXXX
the horizontal scrollbar should not fall oout of the view
we also don't do that for the vertical scrollbar, 
If the ng-grid is places in a container that doesn't allow overflow then
the horizontal will never be shown..
Merge pull request #2004 from mathiasdose/doc-update

Update doc on registerRowBuilder
Merge pull request #2003 from mathiasdose/demoPatch

Correct demo beacuse of exception
Release v3.0.0-rc.13
Fix callDataChangeCallbacks - pass grid to callback
fix(bower): Use right angular version spec

Also include full list of "release" files in "main" specification in
bower.json
Release v3.0.0-rc.14
Merge pull request #2016 from brianchance/master

Fix callDataChangeCallbacks - pass grid to callback
Merge pull request #2009 from Servoy/scrollbars2

scrollbars can be enabled per instance in 3 modes: always,never or when_needed
Merge pull request #2008 from Envisage/master

include header,footer,scrollbar when calculating initial grid height
Merge pull request #2006 from mathiasdose/issue#1955

Fix #1955 (expandable): Left panel features coexistance
Enh(menus): simplify animation, add back tests for 1.2.8 as no mock needed

Use css only for animations, which allows us to avoid using ngAnimateMock, and
simplifies the code a lot.  Minor fix to column positioning when using animations.
Since we're no longer using ngAnimateMock we can test back to 1.2.8 again, have
dropped 1.2.21 to make room.
Merge pull request #2021 from PaulL1/animations_1.2

Enh(menus): simplify animation, add back tests for 1.2.8 as no mock need...
enh(memory leak testing): added a test case

If you navigate to http://localhost:9002/misc/demo/leak-testing.html you
will see a leak testing demo page.

The process on Chrome, using the profiler from Chrome developer tools, is:

1. Navigate around the pages a bit to cache whatever Chrome might cache
2. Go to the home page
3. Take a snapshot from the profile tab
4. Go to the noOptions page
5. Return to the home page
6. Take another snapshot on the profile tab
7. Select to display the difference between snapshot 1 and 2 (right below the menu bar in the profile tab).  At present you'll see about 250K of retained memory
Merge pull request #2022 from PaulL1/memory_leak

enh(memory leak testing): added a test case