mirror of
https://github.com/ionic-team/ionic-framework.git
synced 2026-03-13 10:22:08 +08:00
docs(navView): forward view caching
This commit is contained in:
11
js/angular/directive/navView.js
vendored
11
js/angular/directive/navView.js
vendored
@@ -86,7 +86,16 @@
|
||||
* are being disconnected from the watch cycle. Because scopes are not being destroyed and
|
||||
* recreated, controllers are not loading again on a subsequent viewing. If the app/controller
|
||||
* needs to know when a view has entered or has left, then view events emitted from the
|
||||
* {@link ionic.directive:ionView} scope, such as `$ionicView.enter`, may be useful
|
||||
* {@link ionic.directive:ionView} scope, such as `$ionicView.enter`, may be useful.
|
||||
*
|
||||
* By default, when navigating back in the history, the "forward" views are removed from the cache.
|
||||
* If you navigate forward to the same view again, it'll create a new DOM element and controller
|
||||
* instance. Basically, any forward views are reset each time. This can be configured using the
|
||||
* {@link ionic.provider:$ionicConfigProvider}:
|
||||
*
|
||||
* ```js
|
||||
* $ionicConfigProvider.views.forwardCache(true);
|
||||
* ```
|
||||
*
|
||||
* #### Disable cache globally
|
||||
*
|
||||
|
||||
Reference in New Issue
Block a user