This comment was originally written by joh...@johnmccutchan.com

Correct:

With the ../../../ the application works under dart2js but not Dartium
Without the ../../../ the application works under Dartium but not dart2js.

This comment was originally written by joh...@johnmccutchan.com

s/Correct:/Correction:

Added Area-Polymer, Triaged labels.

John - can you remind us is this with 0.9.5 or 0.10.0-dev.9?

This comment was originally written by joh...@johnmccutchan.com

I'm using 1.4.0.dev_04_00

Sorry, I was wondering about the version of the polymer package, since both 0.9.5+1 and 0.10.0-dev.9 are supported in the 1.4 SDK.

I addressed some of these issues in 0.10.0-dev.9, but I'm not sure if they are enough to fix your issue. Can you give me some pointers on how to try out building observatory?

Thanks!

This comment was originally written by joh...@johnmccutchan.com

Hi,

We use the dev channel release of the SDK (latest 1.4.0 dev release).

name: observatory
version: 0.1.9
dependencies:
  polymer: any
  logging: any
transformers:

• polymer:
      entry_points:
        - web/index.html
        - web/index_devtools.html

We talked about this offline, but just to bring the bug up to date. This resolves to polymer 0.9.5+2, which is the latest released version of polymer, the "-dev" versions are considered pre-releases and pub gives priority to released versions if they are available in your version constraint (in your case "any").

We should give 0.10.* a try with your code to make sure that this issue was resolved. If so, we should consider doing the upgrade. There were some breaking changes that we announced in the mailing list, we also have pending to update the documentation to include more details.

An unrelated comment: it might be worth changing your polymer constraint to something else, for example:

  polymer: ">=0.9.0 <0.10.0"

instead of "any". When we finally release 0.10, using 'any' will cause that once you call 'pub upgrade' the app will likely stop working. If you want to be more in control of when you move from one version to a newer version that has breaking changes, it's a good idea to include an upperbound on the constraint.

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

John McCutchan - now that you are on polymer 0.11.0, is this still an issue?

Added this to the 1.6 milestone.
Removed Priority-Unassigned label.
Added Priority-Medium, NeedsInfo labels.

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

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

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

Added PolymerMilestone-Next label.

Removed Polymer-Milestone-Next label.

Pinging @­johnmccutchan - is this still an issue?

This comment was originally written by @zoechi

As far as I know this is solved since a while.

It is still bothersome that DartEditor (and also WebStorm) can't work with the path Polymer expects. Polymer needs one ../ more than the tools expect therefore navigating from the import link element to the imported html file doesn't work.

After removing one ../ navigating to the imported file works but then pub serve complains.

Good point @­gzoechi, that makes sense - we should create some bugs to track adding support for 'packages/' imports in HTML imports on tools like the editor and webstorm.

I created this bug about adding more documentation for these imports, so we can refer to is from other bugs as well: dart-archive/www.dartlang.org#916

Added AssumedStale label.

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