fixed class name in setButtonShown method, ionList directive
fix(templateCache): make sure $state is passed config options before checking what they are
Merge pull request #2186 from IonDriveSoftware/master

fix(sideMenu): set default width
fix(menuClose): do not close if aside exposed
Merge pull request #2055 from bianchimro/issue-2053

fix(reorder): remove correct class w/in setButtonShown
fix(splitView): disable menu toggles on exposed aside

Closes #2182
fix(scrollView): check that element has not yet been GC'd before removing event listeners in $destroy
chore(collection repeat): commenting out noisy console log
fix(scroll): ensure scrollView objects exist

Check if scrollView is null when switching off of tabs view. #2181
refactor(tabs): prevent unnecessary updates during destroy

If the containing ionTabs directive is being destroyed, then child
ionTab directives should not don't bother going through its
controller’s `remove` method, which selects a new active tab as each
ionTab is being destroyed. By selecting a new active tab as each tab is
removed, it causes unnecessary view loads, transitions and multiple
`viewState.changeHistory` events.
fix(card): less intense box shadow
refactor(popover): popover-top as the default
fix(popup): fill popup width of Android 4.1-4.3 buttons

Closes #2209
fix(popup): set popup head padding equal to popup body padding
fix(keyboard): android scroll stuck

When a state change happens, ensure the keyboard is hidden. When a
keyboard is hidden, ensure all pending timers our cleared. When
resetting scrollView, ensure it’s only doing it when it has to.
For testing: #1670 #2192
fix(exposeAsideWhen): disable with isEnabled=false

Closes #2210
fix(click): remove native click prevent 400ms later

When an actionsheet/popup is open, everything under it has
`pointer-events:none`. However, once they are removed then the click
prevent was removed immediately too, but the click that comes in 300ms
later was still firing whatever would have been underneath the
actionsheet/popup. Instead, wait 400ms before removing the click
prevent, which would block the native click. Closes #2204
test(): fix $timeout.flush
chore(): remove console.log
fix(history): tabs lose history after switching tabs

It was possible that when switching between tabs, and creating a
navigation history in one of the tabs, then switching tabs again, it
could clear out the individual tab stacks under certain scenarios.
Closes #1978