diff options
Diffstat (limited to 'docs/content/guide/dev_guide.services.$location.ngdoc')
| -rw-r--r-- | docs/content/guide/dev_guide.services.$location.ngdoc | 9 |
1 files changed, 4 insertions, 5 deletions
diff --git a/docs/content/guide/dev_guide.services.$location.ngdoc b/docs/content/guide/dev_guide.services.$location.ngdoc index 8270b898..81fd0021 100644 --- a/docs/content/guide/dev_guide.services.$location.ngdoc +++ b/docs/content/guide/dev_guide.services.$location.ngdoc @@ -73,10 +73,9 @@ Any time your application needs to react to a change in the current URL or if yo the current URL in the browser. ## What does it not do? -Does not cause a full page reload when the browser URL is changed. To reload the page after +It does not cause a full page reload when the browser URL is changed. To reload the page after changing the URL, use the lower-level API, `$window.location.href`. - # General overview of the API The `$location` service can behave differently, depending on the configuration that was provided to @@ -133,12 +132,12 @@ current URL without creating a new browser history record you can call: // or you can chain these as: $location.path('/someNewPath').replace(); </pre> -Note that the setters don't update `window.location` immediately. Instead, `$location` service is +Note that the setters don't update `window.location` immediately. Instead, the `$location` service is aware of the {@link api/ng.$rootScope.Scope scope} life-cycle and coalesces multiple `$location` mutations into one "commit" to the `window.location` object during the scope `$digest` phase. Since multiple changes to the $location's state will be pushed to the browser as a single change, it's enough to call the `replace()` method just once to make the entire "commit" a replace operation -rather than addition to the browser history. Once the browser is updated, the $location service +rather than an addition to the browser history. Once the browser is updated, the $location service resets the flag set by `replace()` method and future mutations will create new history records, unless `replace()` is called again. @@ -304,7 +303,7 @@ history API or not; the `$location` service makes this transparent to you. ### Html link rewriting -When you use the history API mode, you will need different links in different browser, but all you +When you use HTML5 history API mode, you will need different links in different browsers, but all you have to do is specify regular URL links, such as: `<a href="/some?foo=bar">link</a>` When a user clicks on this link, |