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

'XSLTProcessor' is undefined in IE11 #213

Open
profnimrod opened this Issue Sep 22, 2014 · 4 comments

Comments

Projects
None yet
2 participants
@profnimrod

profnimrod commented Sep 22, 2014

'XSLTProcessor' is undefined error is throw in IE11 when trying to edit an article. Some insights to the issue might be available at: http://stackoverflow.com/questions/18891860/xslt-processing-on-ie11. The source of the error is in editor_plugin.js

@profnimrod

This comment has been minimized.

Show comment
Hide comment
@profnimrod

profnimrod Dec 5, 2014

When might there be some progress made on this? More than half of our potential authors are using IE11, and cannot do the simplest things with the editor because of this problem.

profnimrod commented Dec 5, 2014

When might there be some progress made on this? More than half of our potential authors are using IE11, and cannot do the simplest things with the editor because of this problem.

@carlthewebmaster

This comment has been minimized.

Show comment
Hide comment
@carlthewebmaster

carlthewebmaster Dec 5, 2014

Contributor

Sorry for the lack of a response. I can look into a fix, but for now the workaround is either to modify the code yourself as indicated in the StackOverflow link (and feel free to submit a pull request if you do!), or have the authors use Chrome or Firefox.

Contributor

carlthewebmaster commented Dec 5, 2014

Sorry for the lack of a response. I can look into a fix, but for now the workaround is either to modify the code yourself as indicated in the StackOverflow link (and feel free to submit a pull request if you do!), or have the authors use Chrome or Firefox.

@profnimrod

This comment has been minimized.

Show comment
Hide comment
@profnimrod

profnimrod Dec 6, 2014

No problem Carl. I did try but for some reason the fix didn't work for me. If I figure the specific code change out I will indeed submit a pull request.

profnimrod commented Dec 6, 2014

No problem Carl. I did try but for some reason the fix didn't work for me. If I figure the specific code change out I will indeed submit a pull request.

@profnimrod

This comment has been minimized.

Show comment
Hide comment
@profnimrod

profnimrod Dec 13, 2014

I had a try today but unfortunately failed... it isn't a case of just simply setting n =new ActiveXObject("Msxml2.XSLTemplate") for IE. Interestingly, on the same Stack Overflow page above (http://stackoverflow.com/questions/18891860/xslt-processing-on-ie11) 'Spudley' notes that "the Chrome devs recently proposed removing their built-in xslt processor on the grounds that no-one uses it...you might want to re-think relying on it being built into the browser". Have you considered using something like Saxon CE (http://www.saxonica.com/ce/index.xml) so you have better cross-browser support?

profnimrod commented Dec 13, 2014

I had a try today but unfortunately failed... it isn't a case of just simply setting n =new ActiveXObject("Msxml2.XSLTemplate") for IE. Interestingly, on the same Stack Overflow page above (http://stackoverflow.com/questions/18891860/xslt-processing-on-ie11) 'Spudley' notes that "the Chrome devs recently proposed removing their built-in xslt processor on the grounds that no-one uses it...you might want to re-think relying on it being built into the browser". Have you considered using something like Saxon CE (http://www.saxonica.com/ce/index.xml) so you have better cross-browser support?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment