-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need consistent path behavior #651
Comments
I noticed this same issue here: It goes a little further than hash links. Every relative path is relative to the imported document. This makes sense for |
Ping? Bumping priority as we're running into it with a large 🎅 project. My current workaround is elliot's, which is to use an expression + baseURI
|
Yes, we're hoping for a fix for use on a big project too. I think @erikringsmuth's idea of treating anchor tags differently may be the ideal approach. |
@sorvell, was it intentional to rewrite |
Yes, the idea is that you should always be able to link resources with paths relative to the importing document. If it's an absolute url or a # based one we should bail. |
The rewriter doesn't check that the node is an anchor, it just rewrites href. The simplest fix is to ignore hash-only hrefs for rewriting. |
Original thread: https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/polymer-dev/JcBQZCPamcY/OMKhLetXg-4J
If I create an element that looks like this:
and then import it into my project, it will treat the
href
s differently. Thehref
's inside of the repeating template will look like this:but the
href
outside of the repeating template will look like this:The text was updated successfully, but these errors were encountered: