The gestures which were being added to side menu content were also
adding the `disable-user-behavior` class, which disabled
contenteditable elements. Now passing in the gesture option
stop_browser_behavior=false, along with adding the options param to the
gestures service. Fixes#421
Many services/directives have to interact with the body element, and
each one has to write the same long code. The $ionicBody service
provides some useful methods to clean up and reduce redundant code.
When a list was within a side menu it could scroll up and down, but if
the user happened to drag a little bit on the X axis, then it would try
to open the side menu and the Y scroll of the content stopped. Closes
#1541
If a menu was opened when navigating to a different view, it is
possible that the `menu-open` class was left on the body tag, which
disables the elements on the next side menu view. On side menu destroy,
ensure menu-open was removed from the body class.
Closes#1741
BREAKING CHANGE:
ion-radio no longer has an isolate scope.
This will break your radio only if you were relying upon the radio having an isolate scope: if you were referencing `$parent.value` as
the ng-disabled attribute, for example.
Change your code from this:
<ion-radio ng-disabled="{{$parent.isDisabled}}"></ion-radio>
To this:
<ion-radio ng-disabled="{{isDisabled}}"></ion-radio>
Closes#1349, #1741
BREAKING CHANGE:
ion-toggle no longer has an isolate scope.
This will break your toggle only if you were relying upon the toggle
having an isolate scope: if you were referencing `$parent.value` as
the ng-disabled attribute, for example.
Change your code from this:
<ion-toggle ng-disabled="{{$parent.isDisabled}}"></ion-toggle>
To this:
<ion-toggle ng-disabled="{{isDisabled}}"></ion-toggle>
Closes#1668.
`<div class="modal">` will still work, but adding an `<ion-modal-view>`
element to wrap a modal template is a more "Ionic Looking" way of doing
the same thing.
