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

namespace support #34

Open
pkra opened this issue May 26, 2017 · 7 comments
Open

namespace support #34

pkra opened this issue May 26, 2017 · 7 comments

Comments

@pkra
Copy link

pkra commented May 26, 2017

ctop currently breaks when content has namespace prefixes.

In particular, it cannot be used together with mml3.js

@dpvc
Copy link
Member

dpvc commented May 30, 2017

Can you provide a test case? I'm having trouble producing one myself.

@pkra
Copy link
Author

pkra commented May 30, 2017

I had noticed this on https://rawgit.com/pkra/MathJax-single-file/master/test/dynamic.html?MathMLSVGTeX (but now I see that build doesn't work for some reason). Let me see if I can make a minimal example.

@pkra
Copy link
Author

pkra commented May 30, 2017

If you add the extension to https://codepen.io/pkra/pen/OPjzqa?editors=1010, it exhibits the problem.

@pkra
Copy link
Author

pkra commented May 30, 2017

And with the extension I mean content-mathml.js.

@dpvc
Copy link
Member

dpvc commented May 30, 2017

OK, thanks, I now have an example to work from.

@dpvc
Copy link
Member

dpvc commented May 30, 2017

I have proposed a fix in mathjax/MathJax#1775. Are we trying to keep this repo in synch with the copy in MathJax? If so, there are previous changes that weren't included here, so they would want to be ported back to this repo.

@pkra
Copy link
Author

pkra commented May 30, 2017

Are we trying to keep this repo in synch with the copy in MathJax? If so, there are previous changes that weren't included here, so they would want to be ported back to this repo.

I remember wanting to ask the same thing back then.

I'm guessing a v3 version will be more stand-alone again so I'm good with leaving it in the core.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants