Arthur Evans

Thanks @StokeMasterJack. Here's what the docs should clarify: - The `dropdown-content` class isn't used for styling, at all. It's used to _identify the element that's going to be used as...

Yes, but: docs aren't getting picked up on the catalog: https://elements.polymer-project.org/elements/paper-dropdown-menu I think it just needs to get added to bower.json for the catalog's sake.

Adding this to the docs is also a good idea. This and the auto-generated change events (property-changed) are subtleties that are obvious to the folks writing the API docs, but...

For the events, I was thinking "Show/Hide generated." Not sure about the flipping attributes/properties ... It makes it more compact but less discoverable (and possibly a little bit opaque).

Yeah, I agree on not repeating them. Just adding an attribute name sounds good.

Because this behavior (and the property-changed events) are specific to Polymer, we should really add them to the autogenerated docs, so users on WC.org don't need to know Polymer-specific conventions...

@justinfagnani Either one will do. I'm having trouble following the issue description, so if you can help with a description or PR, that'd be great. It sounds like maybe the...

Ping. Been seeing a lot of comments about this lately. Is there any way we can do this for 3?

See my comment over here: https://github.com/Polymer/polymer/issues/3348#issuecomment-182766017 I think you can only define a custom property in a rule that matches a custom element (which includes the `:host` selector in an...

My point is that these shouldn't be treated as internals. If you're going to expose a set of theme-able properties and mixins, you need to: 1) Have a file or...