This comment was originally written by @zoechi

I tried to use other paths like the one in the error message but that didn't work in Dartium.

Added Area-Polymer, Triaged labels.

If you make the change that the error message suggests, does it help? :)

Siggi put those in to explain as best as possible what URIs to use. IIRC, the reason isn't actually ImportInliner, it's more about making sure the package can be consumed by other packages and apps without causing canonicalization errors. Basically, the HTML file and Dart files need to end up resolving to one path regardless of where they're imported from.

cc @sigmundch.

This comment was originally written by @zoechi

Using the path in the error message didn't work in Dartium.
I'm actually not sure if I tried pub build with it. I try and post an update.

Interesting. The path with extra ../../ was intended to work in Dartium too. I'm curious, what does the resolved path look like when the app tries to load that URI? how does it differ from the valid path?

This comment was originally written by @zoechi

It works for imports but not for
src="../packages/polymer_ui_elements/polymer_ui_action_icons/action_icons.png"

mmm. Some parts of the system take care of rewriting src urls in 'img' tags, for example, but I'm not sure if we handle this correctly within custom-elements themselves. I'd have to take a closer look.

What's the easiest way to run this? I'm currently trying to checkout polymer_ui_elements and building the 'example' folder (I noticed you are building from another package polymer_ui_elements_example that has a symlink to the examples here, I think now that pub supports building the example folder you shouldn't need that anymore).

Ok, I looked a bit more into this.

There are sort of two issues going on:
 * the main issue is indeed that the 'src' attribute you published in polymer_ui_iconset (and similarly in icon) needs special logic to be resolved correctly (from the context where it is defined, to the context where it is instantiated). We need to make it possible to handle URIs in a consistent manner: resolve correctly any URI that is mentioned in an HTML file. Looking at your comments, it seems that you ran into trouble trying to use baseURI before, so there might be other issues that we need to fix to get that resolved (for example issue #17757).

 * the other issue, which is why you are blocked, is that polymer-build is failing with an error. Turns out this only happens in special attributes like 'src', which we assume to be a URL attribute. I think in this case the polymer-build should give a warning and not an error, so pub-build can continue building your app. I just sent out a change to fix that: https://codereview.chromium.org/221673005/.

In the meantime, the fastest way to get unblocked would be to rename 'src' to something else (e.g. 'src2' would do). Then the polymer build process will not try to rewrite it. We'd still need some logic to adjust the URI later, but at least the build process will generate some output code you can run.

This comment was originally written by @zoechi

Thanks a lot for taking a look so quick.

I renamed the atribute to src2.
Now I get
Exhausted heap space, trying to allocate 96 bytes.

I don't know if this is related but because of this I can't give feedback about your workaround. I'll update when I have more info.

I wonder if this is because there are several examples being compiled. When I tried it I listed only that example in the entrypoints (for example:

transformers:

• polymer:
       entry_points: example/polymer_ui_menu_item/polymer_ui_menu_item.html

) and called 'pub build example'.

This comment was originally written by @zoechi

You are right. Now it works. Thanks again!

This was the first time I successfully built an example page inside the polymer-ui-elements library!
One or two weeks ago this still failed and I had to use and additional package just for building the examples. Great improvement!

This comment was originally written by @zoechi

I spoke too soon #­11. Building examples in polymer_elements package worked only for one entry_point. When I add more the build succeeds but the output doesn't work.

:( - if you haven't already, please file a new bug for the pub folks to know about it.

This comment was originally written by @zoechi

This is a known bug https://code.google.com/p/dart/issues/detail?id=15038
I added my comment only to avoid that someone closes the bug because I stated that it already works ;-)

This comment was originally written by @zoechi

I just found out, that this image reference has a deployment issue. When I deploy the build output to a different directory the image can't be loaded

I get the error that the resource couldn't be found at

• http://erikgrimes.github.io/build_ui/polymer_elements/packages/polymer_ui_elements/polymer_ui_action_icons/action_icons.png
• http://erikgrimes.github.io/polymer_elements/packages/polymer_ui_elements/polymer_ui_action_icons/action_icons.png

when I move the image to this path it works.

This isn't an issue with any of the other resources.

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

This comment was originally written by @zoechi

Is this related to Polymer/old-docs-site#472
I never heard about this logic before. Does Polymer.dart support this?

interesting, I haven't heard of this either, I don't believe we have support for it in polymer.dart.

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

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

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