android13/external/chromium-trace/catapult/third_party/polymer/components/iron-meta
liiir1985 7f62dcda9f initial 2024-06-22 20:45:49 +08:00
..
.github initial 2024-06-22 20:45:49 +08:00
demo initial 2024-06-22 20:45:49 +08:00
test initial 2024-06-22 20:45:49 +08:00
.bower.json initial 2024-06-22 20:45:49 +08:00
.travis.yml initial 2024-06-22 20:45:49 +08:00
CONTRIBUTING.md initial 2024-06-22 20:45:49 +08:00
README.md initial 2024-06-22 20:45:49 +08:00
bower.json initial 2024-06-22 20:45:49 +08:00
hero.svg initial 2024-06-22 20:45:49 +08:00
index.html initial 2024-06-22 20:45:49 +08:00
iron-meta.html initial 2024-06-22 20:45:49 +08:00

README.md

Build status

Demo and API docs

##<iron-meta>

iron-meta is a generic element you can use for sharing information across the DOM tree. It uses monostate pattern 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" value="foo/bar"></iron-meta>

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');

Pure imperative form would be like:

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');

##<iron-meta-query>

iron-meta is a generic element you can use for sharing information across the DOM tree. It uses monostate pattern 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" value="foo/bar"></iron-meta>

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');

Pure imperative form would be like:

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');