Issue metadata
Sign in to add a comment
|
url() resources referenced un <use> takes as base url the current document's url instead of resource's url
Reported by
raul.cha...@gmail.com,
Nov 11 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.89 Safari/537.36 Steps to reproduce the problem: 1. Put both files in the same directory 2. Serve both files staticaly (Just to be able to access the resource, I do not know another way) 3. Open index.html What is the expected behavior? Display a path with red circles in its vertices What went wrong? The red circles are not displayed. In the screenshot can be seen that firefox behaves as expected. Did this work before? N/A Does this work in other browsers? Yes Chrome version: 62.0.3202.89 Channel: stable OS Version: Flash Version: Inspecting with the developer tools the shadow DOM of the use element, it can be noticed that chrome tries to apply index.html#marker as a marker instead of resource.svg#marker. I have noticed the same with filters, so I suspect it applies to all attributes that can take a relative url() value. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by f...@opera.com
, Nov 13 2017Status: Duplicate (was: Unconfirmed)