Link in SVG USE element try load wrong file in IFRAME

Confirmed Issue #8323875

Details

Created
Jul 29, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
25.10586
Reports
Reported by 8 people

Sign in to watch or report this issue.

Steps to reproduce

  1. Create main page with URL like https://main.site.com
  2. Use in page <iframe> with src like https://frame.site.com
  3. In page from https://frame.site.com paste <svg> element with tag <use> and relative link. Like:
<svg>
   <use xlink:href="/static/pack.svg#icon1"></use>
</svg>
  1. Load page from https://main.site.com (with iframe):
  • Expected result: icon shown
  • Actual result:
    • icon not shown
    • Request URL: https://main.site.com/static/pack.svg
    • Status Code 404

! Browser try load pack.svg from main.site.com and not from frame.site.com

Attachments

Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Brad E.”

  • Fixing this is CRITICAL for many business applications

  • Any updates on when this will be fixed Brad E?

  • Well, due to the requirements on this one (SSL,domains) it was hard to get a repro environment running. Ultimately I did get one from IE11, with some slightly different results (I saw it trying to load from main.localhost in my case, as reported - but it also threw a SSL error). Edge for some reason would not load main.localhost despite manually entering the entry into my hosts file. In my environment I used IIS 8, self signed SSL’s and two local websites, main.localhost and frame.localhost. All I could ultimately determine was that IE does indeed throw a request to main.localhost - Chrome and Brave did not do this (Brave threw an error in the console similar to IE - Chrome loaded the SVG without issue. So, not much parity between vendors). 

    I’m having our team investigate in later builds of Win 10 with actual domains and SSL’s. Since this was reported in version 10586, it might have been fixed with the anniversary update (14383). Hope that is the case.

    Best regards,
    The MS Edge Team

  • Microsoft Edge Team

    Changed Assigned To to “Travis L.”

    Changed Assigned To to “Venkat K.”

  • Hi Brad,

    Thanks for the reply, I’ve made a minimal reproduction in a js fiddle that can be found here: http://jsfiddle.net/ovqqmL09/ . This github issue also gives some more context into how the issue is impacting Salesforce users: https://github.com/salesforce-ux/design-system/issues/321 .

    Hope this helps. Please let me know if anything else is needed to reproduce.

    Thanks,
    Mike

  • Thanks, that will help. My repro was not quite as detailed.

  • I did some more testing with browserstack and the fiddle above. It looks like the correct url is hit and the svgs properly render in:
    Safari 5.1
    Chrome 53
    Firefox 48
    Opera 40
    Yandex 14.12

    It failed in:
    Edge 13
    Edge 14

    The OS for all of these tests was windows 10.

  • Microsoft Edge Team

    Changed Assigned To from “Venkat K.” to “Bogdan B.”

    Changed Status to “Confirmed”

  • Thank you for your feedback. This a a known issue and we are already tracking it internally, so I am duping this to our internal issue. Best regards, Francois.

  • Hi Francois,

    Any insight I can give our mutual customers into a resolution timeframe?

    Thanks,
    Mike

  • Sorry, we don’t have specific plans for this bug we can share publicly at this point.

  • Here’s a couple better links for what I mentioned above, dunno how they got combined like that in the editor:

    https://github.com/salesforce-ux/design-system/issues/321

    and

    http://jsfiddle.net/ovqqmL09/

    I’m going to be opening a svg4everybody PR with a workaround for this bug via UA sniffing. I will post back here with that soon.

You need to sign in to your Microsoft account to add a comment.

Sign in