Removed this from the Later milestone.
Added this to the M9 milestone.

Removed this from the M9 milestone.
Added this to the 1.1 milestone.

We can certainly work without the custom element, it's just a little strange if it's not registered. Finding the polymer-element is (currently) a viable way of reflecting on what the custom element can do. And it's kind of neat that the declaration just is the polymer-element.

The easiest fix would be a level of indirection: PolymerDeclaration is no longer a custom element; instead it points at the polymer-element. At that point, we can just leave the polymer-element as whatever it is (either HtmlElement or an upgraded JS custom element).

One of the problems is cases where we haven't seen the PolymerElement yet. Polymer.js delays registration. What we could do here is delay finding polymer-element until your custom-element is created.

But still, finding it would be tricky (linked documents) and add overhead.

I wonder if we can go with a hybrid approach -- if polymer.js is loaded, we do the more expensive search, otherwise we install our own polymer-element that notifies us when it's created so we can remember the association and hook up the element faster.

Removed this from the 1.1 milestone.
Added this to the 1.2 milestone.

Added Library-Polymer label.

fixed a while ago in 0.10.x

Added Fixed label.