From 6cf336ae838a76cd763f28cd76ac1b3d6f9a6709 Mon Sep 17 00:00:00 2001 From: Adam Bradley Date: Fri, 16 Jan 2015 15:45:03 -0600 Subject: [PATCH] docs(navView): forward view caching --- js/angular/directive/navView.js | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/js/angular/directive/navView.js b/js/angular/directive/navView.js index 8eab0eb170..3d84bc8748 100644 --- a/js/angular/directive/navView.js +++ b/js/angular/directive/navView.js @@ -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 *