Evaluation of element demos from PolymerElements

[rictic]

Checkmark indicates that I've opened the element's demo/index.html then poked around and saw no errors on the console and no errors in behavior.

• app-layout
  • Don't AMD transform non-module scripts. #146
• app-route
  • AMD babel helpers clobber the main helpers #147
• google-apis
  • AMD babel helpers clobber the main helpers #147
  • no errors now, I suspect it's broken at master, needs double-checking to be sure
• google-youtube
  • AMD babel helpers clobber the main helpers #147
• iron-a11y-announcer
  • Uncertain. A bit of https://github.com/Polymer/polymer-modulizer/issues/148 was going on, but I couldn't get the announcer to do anything on either the unconverted or converted pages.
• iron-a11y-keys
• iron-a11y-keys-behavior
• iron-ajax
• iron-autogrow-textarea
• iron-behaviors
• iron-checked-element-behavior
• iron-collapse
• iron-component-page
• iron-demo-helpers
  • Linter tries (and fail) to analyze nodejs javascript code. #149
• iron-doc-viewer
• iron-dropdown
  • Separate Babel helpers from RequireJS #152
• iron-fit-behavior
• iron-flex-layout
• iron-form
• iron-form-element-behavior
  • There's a function declared in the script that's referred to by name in the document body. We could consider making all toplevel vars in inline scripts into explicit writes onto the window but that seems excessive to me.
• iron-icon
• iron-icons
• iron-iconset
• iron-iconset-svg
• iron-image
  • Looks like [analyzer] Constructor is discarded from analyzer output #148 is keeping the rendering from being the same across demos?
• iron-input
• iron-jsonp-library
  • AMD babel helpers clobber the main helpers #147
• iron-label
• iron-list
  • Don't AMD transform non-module scripts. #146
  • Don't build when executing test:unit or test:integration #153
• iron-localstorage
• iron-location
• iron-media-query
• iron-menu-behavior
• iron-meta
• iron-overlay-behavior
• iron-pages
• iron-range-behavior
• iron-resizable-behavior
• iron-scroll-target-behavior
• iron-scroll-threshold
• iron-selector
• iron-validatable-behavior
• iron-validator-behavior
• marked-element
• neon-animation
  • Separate Babel helpers from RequireJS #152
• paper-badge
  • Linter tries (and fail) to analyze nodejs javascript code. #149
• paper-behaviors
• paper-button
• paper-card
• paper-checkbox
  • Updates CLI to use '@octokit/rest' instead of 'github'. #154
• paper-dialog
  • Separate Babel helpers from RequireJS #152
  • There's a function declared in the script that's referred to by name in the document body. We could consider making all toplevel vars in inline scripts into explicit writes onto the window but that seems excessive to me.
• paper-dialog-behavior
• paper-dialog-scrollable
• paper-drawer-panel
  • Prepare releases. #155
• paper-dropdown-menu
  • Separate Babel helpers from RequireJS #152
  • Updates CLI to use '@octokit/rest' instead of 'github'. #154
• paper-fab
• paper-header-panel
• paper-icon-button
• paper-input
• paper-item
• paper-linear-progress
• paper-listbox
• paper-material
  • #111 / Integration test: checkout and build 3.0 shop #139
  • [analyzer] Constructor is discarded from analyzer output #148
• paper-menu-button
  • Separate Babel helpers from RequireJS #152
• paper-progress
  • There's a function declared in the script that's referred to by name in the document body. We could consider making all toplevel vars in inline scripts into explicit writes onto the window but that seems excessive to me.
• paper-radio-button
• paper-radio-group
• paper-ripple
• paper-scroll-header-panel
• paper-slider
• paper-spinner
  • There's a function declared in the script that's referred to by name in the document body. We could consider making all toplevel vars in inline scripts into explicit writes onto the window but that seems excessive to me.
• paper-styles
• paper-swatch-picker
  • Separate Babel helpers from RequireJS #152
• paper-tabs
• paper-text-field
• paper-toast
• paper-toggle-button
• paper-toolbar
• paper-tooltip
  • Updates CLI to use '@octokit/rest' instead of 'github'. #154
  • Separate Babel helpers from RequireJS #152
• prism-element

[FluorescentHallucinogen]

@rictic Are there any plans to upgrade GoogleWebComponents?

[rictic]

Yeah, we should add any that are hybrid or that work with 2.0 should be good

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.