Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(53)

Unified Diff: third_party/polymer/v0_8/components-chromium/iron-meta/iron-meta.html

Issue 1155683008: Rename polymer and cr_elements v0_8 to v1_0 (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@v1
Patch Set: fix a merge mistake Created 5 years, 7 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: third_party/polymer/v0_8/components-chromium/iron-meta/iron-meta.html
diff --git a/third_party/polymer/v0_8/components-chromium/iron-meta/iron-meta.html b/third_party/polymer/v0_8/components-chromium/iron-meta/iron-meta.html
deleted file mode 100644
index 2ca804b06da8c25d2bb6c4e17426d8d6cc25978b..0000000000000000000000000000000000000000
--- a/third_party/polymer/v0_8/components-chromium/iron-meta/iron-meta.html
+++ /dev/null
@@ -1,52 +0,0 @@
-<!--
-@license
-Copyright (c) 2015 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">
-
-<!--
-`iron-meta` is a generic element you can use for sharing information across the DOM tree.
-It uses [monostate pattern](http://c2.com/cgi/wiki?MonostatePattern) such that any
-instance of iron-meta has access to the shared
-information. You can use `iron-meta` to share whatever you want (or create an extension
-[like x-meta] for enhancements).
-
-The `iron-meta` instances containing your actual data can be loaded in an import,
-or constructed in any way you see fit. The only requirement is that you create them
-before you try to access them.
-
-Examples:
-
-If I create an instance like this:
-
- <iron-meta key="info" keyUrl="foo/bar"></iron-meta>
-
-Note that keyUrl="foo/bar" is the metadata I've defined. I could define more
-attributes or use child nodes to define additional metadata.
-
-Now I can access that element (and it's metadata) from any iron-meta instance
-via the byKey method, e.g.
-
- meta.byKey('info').getAttribute('keyUrl').
-
-Pure imperative form would be like:
-
- document.createElement('iron-meta').byKey('info').getAttribute('keyUrl');
-
-Or, in a Polymer element, you can include a meta in your template:
-
- <iron-meta id="meta"></iron-meta>
- ...
- this.$.meta.byKey('info').getAttribute('keyUrl');
-
-@group Iron Elements
-@demo demo/index.html
-@hero hero.svg
-@element iron-meta
--->
-
-</head><body><script src="iron-meta-extracted.js"></script></body></html>

Powered by Google App Engine
This is Rietveld 408576698