Roll Polymer

third_party/polymer/v1_0/components-chromium/app-route/app-location.html

Index: third_party/polymer/v1_0/components-chromium/app-route/app-location.html
diff --git a/third_party/polymer/v1_0/components-chromium/app-route/app-location.html b/third_party/polymer/v1_0/components-chromium/app-route/app-location.html
index 4cfc108ce52b8720ead6f824fbbfaee490f96fe1..fa3ca09d7613b00db03b1bfcc29a072720995c03 100644
--- a/third_party/polymer/v1_0/components-chromium/app-route/app-location.html
+++ b/third_party/polymer/v1_0/components-chromium/app-route/app-location.html
@@ -37,13 +37,22 @@ property is then bound into the `app-route` element. The bindings are two-
 directional, so when changes to the `route` object occur within `app-route`,
 they automatically reflect back to the global location.
 
-A `app-location` can be configured to use the hash part of a URL as the
-canonical source for path information.
+### Hashes vs Paths
 
-Example:
+By default `app-location` routes using the pathname portion of the URL. This has
+broad browser support but it does require cooperation of the backend server. An
+`app-location` can be configured to use the hash part of a URL instead using
+the `use-hash-as-path` attribute, like so:
 
     <app-location route="{{route}}" use-hash-as-path></app-location>
 
+### Integrating with other routing code
+
+There is no standard event that is fired when window.location is modified.
+`app-location` fires a `location-changed` event on `window` when it updates the
+location. It also listens for that same event, and re-reads the URL when it's
+fired. This makes it very easy to interop with other routing code.
+
 @element app-location
 @demo demo/index.html
 -->