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 |
deleted file mode 100644 |
index fa3ca09d7613b00db03b1bfcc29a072720995c03..0000000000000000000000000000000000000000 |
--- a/third_party/polymer/v1_0/components-chromium/app-route/app-location.html |
+++ /dev/null |
@@ -1,67 +0,0 @@ |
-<!-- |
-@license |
-Copyright (c) 2016 The Polymer Project Authors. All rights reserved. |
-This code may only be used under the BSD style license found at http://polymer.github.io/LICENSE.txt |
-The complete set of authors may be found at http://polymer.github.io/AUTHORS.txt |
-The complete set of contributors may be found at http://polymer.github.io/CONTRIBUTORS.txt |
-Code distributed by Google as part of the polymer project is also |
-subject to an additional IP rights grant found at http://polymer.github.io/PATENTS.txt |
---><html><head><link rel="import" href="../polymer/polymer.html"> |
-<link rel="import" href="../iron-location/iron-location.html"> |
-<link rel="import" href="../iron-location/iron-query-params.html"> |
-<link rel="import" href="app-route-converter-behavior.html"> |
- |
-<!-- |
-`app-location` is an element that provides synchronization between the |
-browser location bar and the state of an app. When created, `app-location` |
-elements will automatically watch the global location for changes. As changes |
-occur, `app-location` produces and updates an object called `route`. This |
-`route` object is suitable for passing into a `app-route`, and other similar |
-elements. |
- |
-An example of the public API of a route object that describes the URL |
-`https://elements.polymer-project.org/elements/app-route-converter?foo=bar&baz=qux`: |
- |
- { |
- prefix: '', |
- path: '/elements/app-route-converter' |
- } |
- |
-Example Usage: |
- |
- <app-location route="{{route}}"></app-location> |
- <app-route route="{{route}}" pattern="/:page" data="{{data}}"></app-route> |
- |
-As you can see above, the `app-location` element produces a `route` and that |
-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. |
- |
-### Hashes vs Paths |
- |
-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 |
---> |
-</head><body><dom-module id="app-location"> |
- <template> |
- <iron-location path="{{__path}}" query="{{__query}}" hash="{{__hash}}" url-space-regex="{{urlSpaceRegex}}"> |
- </iron-location> |
- <iron-query-params params-string="{{__query}}" params-object="{{queryParams}}"> |
- </iron-query-params> |
- </template> |
- </dom-module> |
-<script src="app-location-extracted.js"></script></body></html> |