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

Simple Mathjax blocks with a single function call display backwards #18

Open
barillax opened this issue Mar 6, 2019 · 4 comments
Open

Comments

@barillax
Copy link

barillax commented Mar 6, 2019

This is an edge case, but I wanted to report it so you were aware (and maybe the fix is easy).

screen shot 2019-03-06 at 3 50 31 pm

CodePen demonstrating the problem: https://codepen.io/barillax/pen/QodJPx

Summary:

If you have a block of MathJax that contains a single number with a bar over it, the number will be flipped horizontally.

I believe this is because the number gets nested inside a span with the mfliph class, but there's no additional surrounding container span that also has mfliph to "cancel out" the horizontal flipping.

You can work around this by including an "empty character" via {} directly in front of the number, as shown in the above example. For some reason, this results in a surrounding container span element with the mfliph class, which fixes the issue.

@barillax
Copy link
Author

barillax commented Apr 25, 2019

Update: this bug also manifests with a \transt{} that is by itself within a MathJax block. See screenshot below, where...

  1. The first example is correct,
  2. The second is incorrect, and
  3. The third is correct after inserting an empty space {} directly before the \transt.

This would also be fixed if there was anything else next to the \transt, such as a period, a surrounding \textcolor, etc.

Screen Shot 2019-04-25 at 10 27 46 AM

@barillax barillax changed the title Single number with a bar is flipped horizontally Simple Mathjax blocks with a single function call display backwards Apr 30, 2019
@barillax
Copy link
Author

barillax commented May 3, 2019

@shadinaif @OmarIthawi just wanted to call out this bug, since it might be an easy fix given how simple the workaround is above!

@OmarIthawi
Copy link
Owner

Thanks @barillax! That sounds like an interesting one. Not sure if we'll get to it soon. Let me know if this is a blocker issue, or if you have other issues.

@barillax
Copy link
Author

barillax commented May 6, 2019

@OmarIthawi no worries, the {} workaround keeps us unblocked for now!

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