You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
export to canvas works ok for me, thank you for the software.
but causes error when trying in firefox, no matter <image / > or <image></image> is used.
errors in can be different -so far i saw
'prefix not bound to namespace' (and it points to when i click the error message),
and 'no closing tag, expected ' or so (and it points just before closing tag then)
it seems that for some reason firefox starts to parse whole window dom tree when it encounters in target svg (and it fails for html5 doc, which is ok). when i remove , export works ok in firefox. in chromium it works finr.
We've also encountered this problem - and by taking a closer look at the svg, it seems that the explicit declaration of xlink is missing in the svg node:
xmlns:xlink="http://www.w3.org/1999/xlink"
Dunno why it is missing, but if it is added manually before forwarding the node, if works fine - at least for data URLs. Maybe you can check if this works in you case as well?
We've also faced this in various versions of IE and Safari; funny to see that it works without this attribute in Chrome/Chromium - it should not.
export to canvas works ok for me, thank you for the software.
but causes error when trying in firefox, no matter <image / > or <image></image> is used.
errors in can be different -so far i saw
'prefix not bound to namespace' (and it points to when i click the error message),
and 'no closing tag, expected ' or so (and it points just before closing tag then)
it seems that for some reason firefox starts to parse whole window dom tree when it encounters in target svg (and it fails for html5 doc, which is ok). when i remove , export works ok in firefox. in chromium it works finr.
generated svg originates from following template:
it produces xlink:href in relative form ('/img/image.jpg'), yet same result i saw when used absolute url
The text was updated successfully, but these errors were encountered: