| Index: third_party/polymer/v1_0/components/iron-meta/iron-meta.html
|
| diff --git a/third_party/polymer/v1_0/components/iron-meta/iron-meta.html b/third_party/polymer/v1_0/components/iron-meta/iron-meta.html
|
| index 10addd767bc4e706fd3f8b1629100153b1f03792..4b3431182823c53da1630bbc5ff79ab2c5a9a49d 100644
|
| --- a/third_party/polymer/v1_0/components/iron-meta/iron-meta.html
|
| +++ b/third_party/polymer/v1_0/components/iron-meta/iron-meta.html
|
| @@ -25,25 +25,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
|
| @@ -68,10 +68,6 @@ Or, in a Polymer element, you can include a meta in your template:
|
| /**
|
| * The type of meta-data. All meta-data of the same type is stored
|
| * together.
|
| - *
|
| - * @attribute type
|
| - * @type String
|
| - * @default 'default'
|
| */
|
| type: {
|
| type: String,
|
| @@ -81,10 +77,6 @@ Or, in a Polymer element, you can include a meta in your template:
|
|
|
| /**
|
| * The key used to store `value` under the `type` namespace.
|
| - *
|
| - * @attribute key
|
| - * @type String
|
| - * @default ''
|
| */
|
| key: {
|
| type: String,
|
| @@ -93,10 +85,6 @@ Or, in a Polymer element, you can include a meta in your template:
|
|
|
| /**
|
| * The meta-data to store or retrieve.
|
| - *
|
| - * @attribute value
|
| - * @type *
|
| - * @default this
|
| */
|
| value: {
|
| type: Object,
|
| @@ -106,10 +94,6 @@ Or, in a Polymer element, you can include a meta in your template:
|
|
|
| /**
|
| * If true, `value` is set to the iron-meta instance itself.
|
| - *
|
| - * @attribute self
|
| - * @type Boolean
|
| - * @default false
|
| */
|
| self: {
|
| type: Boolean,
|
| @@ -118,9 +102,6 @@ Or, in a Polymer element, you can include a meta in your template:
|
|
|
| /**
|
| * Array of all meta-data values for the given type.
|
| - *
|
| - * @property list
|
| - * @type Array
|
| */
|
| list: {
|
| type: Array,
|
| @@ -184,8 +165,8 @@ Or, in a Polymer element, you can include a meta in your template:
|
| * Retrieves meta data value by key.
|
| *
|
| * @method byKey
|
| - * @param {String} key The key of the meta-data to be returned.
|
| - * @returns *
|
| + * @param {string} key The key of the meta-data to be returned.
|
| + * @return {*}
|
| */
|
| byKey: function(key) {
|
| return this._metaData && this._metaData[key];
|
| @@ -232,7 +213,7 @@ Or, in a Polymer element, you can include a meta in your template:
|
|
|
| <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-query` instance:
|
| @@ -251,10 +232,6 @@ Or, in a Polymer element, you can include a meta in your template:
|
| /**
|
| * The type of meta-data. All meta-data of the same type is stored
|
| * together.
|
| - *
|
| - * @attribute type
|
| - * @type String
|
| - * @default 'default'
|
| */
|
| type: {
|
| type: String,
|
| @@ -265,9 +242,6 @@ Or, in a Polymer element, you can include a meta in your template:
|
| /**
|
| * Specifies a key to use for retrieving `value` from the `type`
|
| * namespace.
|
| - *
|
| - * @attribute key
|
| - * @type String
|
| */
|
| key: {
|
| type: String,
|
| @@ -276,10 +250,6 @@ Or, in a Polymer element, you can include a meta in your template:
|
|
|
| /**
|
| * The meta-data to store or retrieve.
|
| - *
|
| - * @attribute value
|
| - * @type *
|
| - * @default this
|
| */
|
| value: {
|
| type: Object,
|
| @@ -289,9 +259,6 @@ Or, in a Polymer element, you can include a meta in your template:
|
|
|
| /**
|
| * Array of all meta-data values for the given type.
|
| - *
|
| - * @property list
|
| - * @type Array
|
| */
|
| list: {
|
| type: Array,
|
| @@ -304,7 +271,7 @@ Or, in a Polymer element, you can include a meta in your template:
|
| * Actually a factory method, not a true constructor. Only runs if
|
| * someone invokes it directly (via `new Polymer.IronMeta()`);
|
| */
|
| - constructor: function(config) {
|
| + factoryImpl: function(config) {
|
| if (config) {
|
| for (var n in config) {
|
| switch(n) {
|
| @@ -337,10 +304,8 @@ Or, in a Polymer element, you can include a meta in your template:
|
|
|
| /**
|
| * Retrieves meta data value by key.
|
| - *
|
| - * @method byKey
|
| - * @param {String} key The key of the meta-data to be returned.
|
| - * @returns *
|
| + * @param {string} key The key of the meta-data to be returned.
|
| + * @return {*}
|
| */
|
| byKey: function(key) {
|
| return this._metaData && this._metaData[key];
|
|
|