-
Notifications
You must be signed in to change notification settings - Fork 88
2 fragments using the same name but from 2 different files conflicts #99
Comments
might it be because of the #arrival symbol? |
It could be 2 times #departure the result will be the same. I suspect some cache to use the fragment name as the key. |
This is indeed because of the same IDs, which this directive doesn't try to distinguish between. It'll use whichever instance of the ID shows up first on the page (since they're injected directly into the DOM). Ideally, the symbol IDs would be different. |
@arkon sometimes we do not choose the name of the fragment. The namespace should be the file path (url) which will be unique per svg file, not the fragment (symbol) name |
why setting |
The cache is irrelevant to how things are rendered. Still not entirely sure how this should be solved. |
From #114:
|
Renders
while inverting those lines
gives:
despite the cache to be disabled, the first object will be reused by the second one
SVGs.zip
The text was updated successfully, but these errors were encountered: