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

"Show math as TeX Commands" no longer works #395

Closed
aleth opened this Issue Feb 16, 2013 · 5 comments

Comments

Projects
None yet
3 participants
@aleth

aleth commented Feb 16, 2013

With Mathjax 2.1 and Firefox>=18 (possibly earlier versions too, but I remember it working some time ago), the Latex source is no longer displayed on selecting "TeX Commands" from the context menu. Instead, nothing happens.

@aleth

This comment has been minimized.

aleth commented Feb 16, 2013

There is an error in the error console:
Error: TypeError: window.open is not a function
Source File: http://cdn.mathjax.org/mathjax/latest/config/TeX-AMS-MML_HTMLorMML.js
Line: 58

The same source file produces a lot of warnings by the way, even before attempting to show the source. ReferenceErrors, SyntaxErrors, TypeErrors - not very reassuring.

@pkra

This comment has been minimized.

Member

pkra commented Feb 20, 2013

I cannot reproduce this using FF 18.0.2 on linux. Do you have a specific page where this occurs or is this a general problem?

@dpvc

This comment has been minimized.

Member

dpvc commented Feb 20, 2013

I can't reproduce it either, in FF 18.0.1 or FF 19.0 on Mac OS X. I see a couple of warnings about deprecated attributes and a couple CSS warnings, but nothing like what aleth suggests.

Is this on your own pages or on all pages (like the ones at www.mathjax.org)?

@aleth

This comment has been minimized.

aleth commented Feb 21, 2013

I had tested it on www.mathjax.org (for me, it is a general problem). However, I just discovered I can't reproduce the problem with a clean profile on FF20, so there is probably some interaction with an add-on going on. Sorry for the false alarm!

dpvc: To see the warnings, set javascript.options.strict=true in about:config. (I had this turned on for some development work, and to see whether I could gather some more information before reporting the bug.) Of course, these warnings probably don't reflect bugs, but they are very noisy.

@pkra

This comment has been minimized.

Member

pkra commented Feb 21, 2013

Thanks for checking this again. Any idea which add-on might be at fault? (I'm guessing a pop-up blocker)

@pkra pkra closed this Feb 21, 2013

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