validator.ampproject.orgThe AMP Validator

* * Other expressions that are noted include: * * Double-mustache annotations in text content. The annotation must be the only * content in the tag, compound expressions are not (currently) supported. * * {{path.to.host.property}} * * Double-mustache annotations in an attribute. * * * * Only immediate host properties can automatically trigger side-effects. * Setting `host.path` in the example above triggers the binding, setting * `host.path.to.host.property` does not. * * `on-` style event declarations. * * ="{{hostMethodName}}" * * Note: **the `annotations` feature does not actually implement the behaviors * associated with these expressions, it only captures the data**. * * Other optional features contain actual data implementations. * * @class standard feature: annotations */ /* Scans a template to produce an annotation map that stores expression metadata and information that associates the metadata to nodes in a template instance. Supported annotations are: * id attributes * binding annotations in text nodes * double-mustache expressions: {{expression}} * double-bracket expressions: [[expression]] * binding annotations in attributes * attribute-bind expressions: name="{{expression}} || [[expression]]" * property-bind expressions: name*="{{expression}} || [[expression]]" * property-bind expressions: name:="expression" * event annotations * event delegation directives: on- ="expression" Generated data-structure: [ { id: ’ ’, events: [ { mode: [’auto’|’’], name: ’ ’ value: ’ ’ }, ... ], bindings: [ { kind: [’text’|’attribute’|’property’], mode: [’auto’|’’], name: ’ ’ value: ’ ’ }, ... ], // TODO(sjmiles): confusingly, this is annotation-parent, not node-parent parent: , index: }, ... ] TODO(sjmiles): this module should produce either syntactic metadata (e.g. double-mustache, double-bracket, star-attr), or semantic metadata (e.g. manual-bind, auto-bind, property-bind). Right now it’s half and half. */ Polymer.Base._addFeature({ // registration-time _prepAnnotations: function() { if (!this._template) { this._notes = []; } else { // TODO(sorvell): ad hoc method of plugging behavior into Annotations var self = this; Polymer.Annotations.prepElement = function(element) { self._prepElement(element); } if (this._template._content && this._template._content._notes) { this._notes = this._template._content._notes; } else { this._notes = Polymer.Annotations.parseAnnotations(this._template); this._processAnnotations(this._notes); } Polymer.Annotations.prepElement = null; } }, _processAnnotations: function(notes) { for (var i=0; i ... ``` Note, all features of `custom-style` are available when defining styles as part of Polymer elements (e.g. ` Title ``` `paper-toolbar` has a standard height, but can made be taller by setting `tall` class on the `paper-toolbar`. This will make the toolbar 3x the normal height. ```html ``` Apply `medium-tall` class to make the toolbar medium tall. This will make the toolbar 2x the normal height. ```html ``` When `tall`, items can pin to either the top (default), middle or bottom. Use `middle` class for middle content and `bottom` class for bottom content. ```html Middle Title Bottom Title ``` For `medium-tall` toolbar, the middle and bottom contents overlap and are pinned to the bottom. But `middleJustify` and `bottomJustify` attributes are still honored separately. To make an element completely fit at the bottom of the toolbar, use `fit` along with `bottom`. ```html ``` When inside a `paper-header-panel` element, the class `.animate` is toggled to animate the height change in the toolbar. ### Styling The following custom properties and mixins are available for styling: Custom property | Description | Default |-| `paper-toolbar-title` | Mixin applied to the title of the toolbar | `{}` `paper-toolbar-background` | Toolbar background color | `primary-color` `paper-toolbar-color` | Toolbar foreground color | `dark-theme-text-color` `paper-toolbar-height` | Custom height for toolbar | `64px` `paper-toolbar-sm-height` | Custom height for small screen toolbar | `56px` `paper-toolbar` | Mixin applied to the toolbar | `{}` `paper-toolbar-content` | Mixin applied to the content section of the toolbar | `{}` `paper-toolbar-medium` | Mixin applied to medium height toolbar | `{}` `paper-toolbar-tall` | Mixin applied to tall height toolbar | `{}` `paper-toolbar-transition` | Transition applied to the `.animate` class | `height 0.18s ease-in` ### Accessibility ` ` has `role="toolbar"` by default. Any elements with the class `title` will be used as the label of the toolbar via `aria-labelledby`. @demo demo/index.htmlHOWTO GITHUB PRIVACY CHROME EXTENSION VSCODE EXTENSION NPM ... content ... @group Paper Elements @demo demo/index.htmlExample setting size to 32px x 32px: The iron elements include several sets of icons. To use the default set of icons, import `iron-icons.html` and use the `icon` attribute to specify an icon: To use a different built-in set of icons, import the specific `iron-icons/ -icons.html`, and specify the icon as ` : `. For example, to use a communication icon, you would use: You can also create custom icon sets of bitmap or SVG icons. Example of using an icon named `cherry` from a custom iconset with the ID `fruit`: See [iron-iconset](iron-iconset) and [iron-iconset-svg](iron-iconset-svg) for more information about how to create a custom iconset. See the [iron-icons demo](iron-icons?view=demo:demo/index.html) to see the icons available in the various iconsets. ### Styling The following custom properties are available for styling: Custom property | Description | Default |-| `iron-icon-width` | Width of the icon | `24px` `iron-icon-height` | Height of the icon | `24px` `iron-icon-fill-color` | Fill color of the svg icon | `currentcolor` `iron-icon-stroke-color` | Stroke color of the svg icon | none @group Iron Elements @element iron-icon @demo demo/index.html @hero hero.svg @homepage polymer.github.ioNote 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: ... this.$.meta.byKey(’info’); @group Iron Elements @demo demo/index.html @hero hero.svg @element iron-metaValidation Status: {{status}} Review our ’ publishing checklist ’ to ensure successful AMP document distribution. ` implements an accessible listbox control with Material Design styling. The focused item is highlighted, and the selected item has bolded text. Item 1 Item 2 An initial selection can be specified with the `selected` attribute. Item 1 Item 2 Make a multi-select listbox with the `multi` attribute. Items in a multi-select listbox can be deselected, and multiple item can be selected. Item 1 Item 2 ### Styling The following custom properties and mixins are available for styling: Custom property | Description | Default |-| `paper-listbox-background-color` | Menu background color | `primary-background-color` `paper-listbox-color` | Menu foreground color | `primary-text-color` `paper-listbox` | Mixin applied to the listbox | `{}` ### Accessibility ` ` has `role="listbox"` by default. A multi-select listbox will also have `aria-multiselectable` set. It implements key bindings to navigate through the listbox with the up and down arrow keys, esc to exit the listbox, and enter to activate a listbox item. Typing the first letter of a listbox item will also focus it. @group Paper Elements @element paper-listbox @hero hero.svg @demo demo/index.html` is an interactive list item. By default, it is a horizontal flexbox. Item Use this element with ` ` to make Material Design styled two-line and three-line items. Show your status Your status is visible to everyone ### Styling The following custom properties and mixins are...