Steps to reproduce
I’m having issues displaying SVG which is being created dynamically on Edge. This shows correctly on Chrome, Firefox, and Safari apple.
I’m giving you 2 examples. In the first one you will see a whole black image where the plan should actually show. When you hover on the sections the section will be displayed. The 2nd example is another example where the small circles (seats) are shown but then again the text which is embedded in plan is not shown.
Comments and activity
hey just a note I have fixed it. the issue is that ie is having an issue that it’s expecting fill in the svg to be uppercase. So I had to traverse all the elements and set the fill myself. but the bug in edge is still there.
I do not see any problem here using our latest insider preview build, on any of the pages you linked. Which version of EdgeHTML are you running? (Please note this is different from Edge the app, you should find a number between 12 and 15).
Yes as I have said the issue is now solved but I had to resort to doing some code myself to sort it out. I updated my live version to sort it out. The issue seems that the you’re expecting the SVG fill attribute in uppercase.
However look here https://showshappeningmirror.azurewebsites.net/Public-Broadcasting-Services-Limited/Malta-Eurovision-Song-Contest-2017. I replicated the issue on my mirror website.
Also look at this http://canvg.github.io/canvg/examples/index.htm. This is not my website but they also have the same issue.
I am using Microsoft EdgeHTML 14.14393
Thanks, I am able to repro now.
- Microsoft Edge Team
Changed Assigned To to “Ian P.”
Changed Status to “Confirmed”
Changed Title from “SVG Inline shows as blank” to “Some SVG attributes won't get recognized if not set in uppercase, causing blank rendering”
Thanks again. Hopefully it gets fixed soon since it’s quite a big issue, but most prob easily solvable :)
Our next release is scheduled for Windows Creators update and we likely won’t be able to address this issue by then. We usually try to release twice a year, so there should be another opportunity to fix this in 2017.
pity because edge is a new browser and bugs like this on a technology such as svg which is extremely popular nowadays is a killer…