Taylor Savage

I believe @kevinpschaaf mentioned this to me originally

Agreed - we should definitely look into building up a package of content around how to scale Polymer & Web Component deployments at a company. The Summit talks will provide...

@addyosmani I think we're ok for this element set since it's just standard that everything starts with `google-`, like `google-youtube`. I'd say we're good to go to change this.

Another use-case for this we just ran into: serving a static/server-rendered version of a page to bots & crawlers that don't execute JS, and a dynamic one to those that...

Ran into this, and also the inverse - if you don't have a trailing slash on the URL, the carbon-route with a leading slash in the pattern won't match it....

This change totally makes sense to me, to build a bridge for breaking changes we _know_ we're going to introduce in a potential 2.0 of the elements. I agree with...

This is also a material design bug - there is no differentiation in the "icon-toggles" section of the spec between `focused` and `pressed` state. For non-toggle paper-icon-buttons, I think the...

This appears to be how `` [works](http://jsbin.com/pubukesetu/edit?html,js) as well, so I think the current behavior might be the expected behavior. According to the [spec](https://www.w3.org/TR/html5/forms.html#the-form-element) nested forms shouldn't be supported at...

_From @kevinpschaaf on June 15, 2015 19:21_ This issue tracker is for the Polymer core library itself. We'll get this moved to a more appropriate tracker, like `PolymerElements/iron-elements`.

Digging in to some of the material design videos, my guess at the correct behavior might be to wait until the menu area has expanded to its full width before...