| 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 1622a6a557df5f483f840737a26d18cacde1882a..cb9a3973da69c77ececdbf50312d31b507770902 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
|
| @@ -31,17 +31,17 @@ 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('value');
|
| + meta.byKey('info');
|
|
|
| Pure imperative form would be like:
|
|
|
| - document.createElement('iron-meta').byKey('info').getAttribute('value');
|
| + document.createElement('iron-meta').byKey('info');
|
|
|
| Or, in a Polymer element, you can include a meta in your template:
|
|
|
| <iron-meta id="meta"></iron-meta>
|
| ...
|
| - this.$.meta.byKey('info').getAttribute('value');
|
| + this.$.meta.byKey('info');
|
|
|
| @group Iron Elements
|
| @demo demo/index.html
|
|
|