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

Baseline problem with mjpage and CommonHTML under Safari #344

Open
ischurov opened this issue Jul 14, 2017 · 4 comments
Open

Baseline problem with mjpage and CommonHTML under Safari #344

ischurov opened this issue Jul 14, 2017 · 4 comments

Comments

@ischurov
Copy link

I have weird behaviour of MathJax-node, particularly MathJax-node-page, under Safari. Shortly speaking, letters are not vertically aligned properly.

Here is my input. Under ordinary MathJax, I have fine layout.

screen shot 2017-07-14 at 22 25 08

I save this input as test.html, then perform the following command:

./mjpage --output CommonHTML --fontURL https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.1/fonts/HTML-CSS < test.html > test_out.html

Then I have the following output. It renders rather badly under Safari. Look at vertical alignment of the characters.

screen shot 2017-07-14 at 22 28 13

I've tried the latest MathJax-node from github (as well as stable one from npm directory) with the same result. I can reproduce it under mobile Safari from my iPhone as well, but not from in Chrome.

@pkra
Copy link
Contributor

pkra commented Aug 1, 2017

Thanks for the report. I can confirm the issue.

Minimal example at https://codepen.io/pkra/pen/NvNJKy

@pkra
Copy link
Contributor

pkra commented Aug 1, 2017

On looking further into this, it looks related to mathjax/MathJax#1710. On the one hand, zooming into mathjax-node output changes the glitching (sometimes better, sometimes worse). On the other hand, the live version has the same glitches when zooming in/out.

@dpvc what do you think?

@pkra pkra added the Upstream label Aug 1, 2017
@dpvc
Copy link
Member

dpvc commented Aug 26, 2017

Sorry, this fell through the cracks for me. Yes, I suspect this is the known issue with Safari that you mention. There are problems with other WebKit browsers as well, but Safari handles some situations differently from Chrome, for example, and is particularly susceptible to these problems.

@pkra
Copy link
Contributor

pkra commented Aug 28, 2017

@dpvc thanks for confirming.

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

No branches or pull requests

3 participants