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

Content MathML extension fails in IE11 #696

Closed
davidcarlisle opened this issue Dec 16, 2013 · 7 comments

Comments

Projects
None yet
3 participants
@davidcarlisle
Copy link

commented Dec 16, 2013

IE managed to break something again.

In the default "edge" mode the conversion fails to run and so you get an error from the main mathjax processing about an unknown apply node. If you use F12 developer tools to flip it into IE10 mode it works fine.

I started to debug but inconclusively but it's late so I'll not speculate where exactly it's going wrong (the mathjax enabled MathML3 spec at Math/draft-spec/mathml html is similarly broken although that doesn't use this extension.)

A test file for completeness, although any file will show same.

<!DOCTYPE html>
<html>
 <head>
  <title>a+b</title>
  <script type="text/x-mathjax-config">
MathJax.Hub.Config({
MathML: {
extensions: ["content-mathml.js"]
}
});
</script>
<script src="http://cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML"></script>
 </head>

 <body>

  <math>
   <apply><plus/><mi>a</mi><mi>b</mi></apply>   
  </math> 

 </body>
</html>
@dpvc

This comment has been minimized.

Copy link
Member

commented Dec 16, 2013

Thanks, David, we'll check into it.

@davidcarlisle

This comment has been minimized.

Copy link
Author

commented Dec 17, 2013

The failure seems to be in the IE detection The IE debugger reports MathJax.Hub.Browser.isMSIE as false.
If I just make this and the version test force test true as follows: then it works on IE11 with the Content MathML being displayed (that isn't a real fix of course:-)

var d;if(window.XSLTProcessor){if(!c.ParseXML){
c.ParseXML=c.createParser()}c.ctopXSLT=new XSLTProcessor();
c.ctopXSLT.importStylesheet(c.ParseXML(a))}else{if(true){
if(true){
d=new ActiveXObject("Msxml2.FreeThreadedDOMDocument");d.loadXML(a);
@dpvc

This comment has been minimized.

Copy link
Member

commented Dec 17, 2013

Thanks again for the detective work. Yes, IE11 is not being detected properly. Glad that seems to fix it.

@pkra

This comment has been minimized.

Copy link
Member

commented Dec 17, 2013

Does this make it a duplicate of #658 ?

@davidcarlisle

This comment has been minimized.

Copy link
Author

commented Dec 17, 2013

yes looks like it.

@dpvc

This comment has been minimized.

Copy link
Member

commented Jan 10, 2014

Yes, it is a duplicate. I have a work-around for the wrong browser identification, and that fixes this problem as well.

@dpvc

This comment has been minimized.

Copy link
Member

commented Mar 18, 2014

Since #658 is resolved, I'm closing this duplicate as well.

@dpvc dpvc closed this Mar 18, 2014

@dpvc dpvc removed the Accepted label Mar 18, 2014

@dpvc dpvc added v2.4 labels Jun 30, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.