Index: third_party/polymer/v1_0/components-chromium/iron-meta/iron-meta.html |
diff --git a/third_party/polymer/v1_0/components-chromium/iron-meta/iron-meta.html b/third_party/polymer/v1_0/components-chromium/iron-meta/iron-meta.html |
index 2ca804b06da8c25d2bb6c4e17426d8d6cc25978b..e6e151e8c58d401ce1e6cd62c15c1558101fa98b 100644 |
--- a/third_party/polymer/v1_0/components-chromium/iron-meta/iron-meta.html |
+++ b/third_party/polymer/v1_0/components-chromium/iron-meta/iron-meta.html |
@@ -23,25 +23,25 @@ Examples: |
If I create an instance like this: |
- <iron-meta key="info" keyUrl="foo/bar"></iron-meta> |
+ <iron-meta key="info" value="foo/bar"></iron-meta> |
-Note that keyUrl="foo/bar" is the metadata I've defined. I could define more |
+Note that value="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'). |
+ meta.byKey('info').getAttribute('value'). |
Pure imperative form would be like: |
- document.createElement('iron-meta').byKey('info').getAttribute('keyUrl'); |
+ document.createElement('iron-meta').byKey('info').getAttribute('value'); |
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'); |
+ this.$.meta.byKey('info').getAttribute('value'); |
@group Iron Elements |
@demo demo/index.html |