bug report here: https://groups.google.com/a/dartlang.org/d/msg/web/Dog6SQ6oy84/bWEfpJntjmAJ

and a pull request illustrating workaround: montyr75/remember_me#1

bumping priority since at least two people have hit it now. Also it's a difference between Dartium and dart2js, so you don't catch it at development time

Removed Priority-Unassigned label.
Added Priority-High label.

Added this to the 1.4 milestone.

Removed this from the 1.4 milestone.
Added this to the Polymer0.10 milestone.

Issue #18794 has been merged into this issue.

Added Pkg-Polymer label.

Removed Pkg-Polymer label.
Added Pkg-PolymerBuild label.

Removed Library-PolymerBuild label.

Removed Area-Polymer label.
Added Area-Pkg label.

Removed this from the Polymer0.10 milestone.
Added this to the 1.6 milestone.

Removed this from the 1.6 milestone.
Added Polymer-P-1 label.

Removed Polymer-P-1 label.
Added Polymer-Milestone-Next label.

Added PolymerMilestone-Next label.

Removed Polymer-Milestone-Next label.

Added this to the 1.6 milestone.

It looks like the linter is catching this now at least, but it would still be good to make it work.

Set owner to @jakemac53.
Added Started label.

There are basically 3 options that I see here:

1. Enable general nested polymer-element elements. The fix for this is pretty easy and I have a cl that works (at least in the simple cases), but this would need to be supported on the javascript side as well and its questionable as to whether its something they/we really want to support long term.
2. Fix this in the build step for people automatically. In that case it would actually be broken for people who are running it in Dartium though without building first (it does not actually fully work as it first appears).
3. Leave it as is with the linter warning and enforce that people just don't nest polymer elements and put their imports outside polymer-elements. I don't know of a legitimate use case for nesting polymer-elements, and we could always add support for it in the future if somebody does come up with one.

Me and sigmund@ are going to chat with the Polymer JS team and see what they have to say about supporting nested polymer-elements since we should be on the same page in order to inter-op effectively.

We decided the best course of action was to follow whatever vulcanizer does to keep the two projects consistent. Vulcanizer currently does exactly what we are doing, so we are going to leave it as is, just with the linter warning.

Added WontFix label.

This issue has been moved to dart-archive/polymer-dart#388.