Parse XML from string instead of using external file
Closed this issue · 2 comments
Updated issue:
Parse XML from string instead of using external file
In order to deal with the Chrome bug, while keeping the libraries loading modular, a different method will be used. A separate libloader.js file will be used to load the required library files from a string containing the XM data instead of a separate XML file. This should make the solution cross-browser and allow for it to be modular as before.
Original issue:
Chrome cannot fetch libraries from local file
There is a bug with chrome at the moment not allowing local xmlhttpopen() requests which can be a problem with the library loading.
There will be a workaround provided that loads the libraries file from this repository, however if an offline, standalone version is to ever be released a fix should be released eventually. ( I read somewhere that disabling a flag in chrome could allow the code that runs on Firefox to run on chrome as well).
9d1a737: Issue resolved, loading is now done via libloader.js. All library data has been moved to this file.