Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IE 10 Security Error CoSe #1215

Closed
johnnyflinn opened this issue Jan 9, 2016 · 2 comments
Closed

IE 10 Security Error CoSe #1215

johnnyflinn opened this issue Jan 9, 2016 · 2 comments
Labels
browser-bug A problem in the browser itself

Comments

@johnnyflinn
Copy link

Looking at the CoSe demo at http://js.cytoscape.org/demos/7b511e1f48ffd044ad66/ , layout fails in IE 10 emulation mode.

Error possible related to http://stackoverflow.com/questions/10343913/how-to-create-a-web-worker-from-a-string

See also parallel-js/parallel.js#12

@maxkfranz maxkfranz added the browser-bug A problem in the browser itself label Jan 11, 2016
@maxkfranz
Copy link
Member

Cytoscape.js uses Weaver.js (weaver.js.org) for multitasking. It uses inline-defined workers in browsers.

It's not possible to work around the issue you've mentioned without creating a separate file just for IE10. A major point of using Weaver threads is that you don't have to fiddle with external file references and minfication settings to get webworkers to work.

I don't think it makes sense to add a workaround for a browser that is two major releases out of date, especially since it creates complications for developers using the library.

Your options are:

(1) Fork the CoSE layout with the thread option { disabled: true }. That way, simulated webworkers in the main thread are used. (Make sure to change the name to something like cose-forked so it doesn't conflict.)

(2) Use a layout other than CoSE. There are many supported in the library and many more as extensions.

(3) Tell your IE10 users to upgrade their browser or (better yet) install a decent browser. Chrome can be installed to a user's home directory -- even on Windows.

@maxkfranz
Copy link
Member

I've added a ticket to Weaver to make this a bit more convenient: maxkfranz/weaver#15

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
browser-bug A problem in the browser itself
Projects
None yet
Development

No branches or pull requests

2 participants