We have site where we use GoJS. In our node templates we use SVG images. Everything worked fine until we started using IdentityServer3 and HTTPS. After that SVG files in our node templates became invisible.
Is it GoJS issue and if so is there a way to overcome it?
This is probably not a CORS issue, but in case it is, there’s some information below on that.
The problem may be that you are not specifying the width and height for your SVG images, but I cannot be sure. Make sure you are folllowing every recommendation here: GoJS Pictures -- Northwoods Software
Once you have width and height set for the SVG (and make sure they equal the width/height that is in the viewport in the .svg definition, do you see anything differently?
If it is a CORS issue (this is unlikely unless you’re calling makeImage), here is a very simple test for CORS:
I am taking an image from Wikipedia and drawing it on the canvas (red), after it is drawn, I use canvas.toDataURL() to copy the canvas to an image (blue). If the cross-origin flag isn’t set, blue won’t work.
Red should work and is what GoJS is doing (unless you call makeImage, then blue needs to work too).
If your images do not work in this simple example, then its not something GoJS is doing, its a canvas or CORs or other issue.