Open ane-gabriela opened 4 years ago
Actual results: The diagram can be edited but there are errors in every browser.
The end users don't care about the logged JavaScript messages as long as the diagram editor works. End users don't open the JavaScript console.
The only remaining error logged on Firefox after closing #192 is the "XML Parsing Error: unclosed token". This is not logged in Chrome so it appears to be specific to Firefox. The issue seems to be related to a SVG image loaded using data URI but it's hard to spot which one and we don't control those SVGs anyway (they come from draw.io library).
Note that I see "XML Parsing Error: unclosed token" logged also when accessing draw.io online so this seems to confirm that this is a draw.io issue related to some SVG image they use and which upsets Firefox (but not Chrome).
Steps to reproduce:
Expected results: The diagram can be edited with no errors in the browser console.
Actual results: There are errors in every browser.
Environment: Windows 10, XWiki 11.10.4 with MySQL 5.7, IE 11, Chrome 81, Firefox 75, Edge 18
IE11![IE11EditingDiagram](https://user-images.githubusercontent.com/40691112/79219894-bdd1fa00-7e5b-11ea-94c8-8e99e3a03eaf.jpg)
Chrome 81![ChromeEditing](https://user-images.githubusercontent.com/40691112/79219844-a72ba300-7e5b-11ea-9974-f606426cabf0.jpg)
Firefox 75![FirefoxEditing](https://user-images.githubusercontent.com/40691112/79219783-91b67900-7e5b-11ea-9388-2ac72b8a2af5.jpg)
Edge 18![EdgeEditing](https://user-images.githubusercontent.com/40691112/79219930-c9bdbc00-7e5b-11ea-962c-d4772dafe7e6.jpg)