-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Line breaking inside shrink-wrap elements doesn't work well #1478
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
Labels
Milestone
Comments
dpvc
added a commit
to dpvc/MathJax
that referenced
this issue
May 17, 2016
…ry to handle the problem with full-width equations being too wide when the ex-size isn't measured accurately enough. Issue mathjax#1478.
dpvc
added a commit
to dpvc/MathJax
that referenced
this issue
May 17, 2016
…L-CSS, and add the CSS from handle-floats into the standard HTML-CSS. Remove the content of the handle-floats extension. Issue mathjax#1478.
dpvc
added a commit
to dpvc/MathJax
that referenced
this issue
May 17, 2016
The |
dpvc
added a commit
to dpvc/MathJax
that referenced
this issue
Jun 8, 2016
dpvc
added a commit
that referenced
this issue
Jun 8, 2016
Properly determine container widths. Resolves issue #1478.
==> Merged. |
dpvc
added a commit
to dpvc/MathJax
that referenced
this issue
Jun 20, 2016
…new width-detection scheme (linebreakSpan). mathjax#1478.
dpvc
added a commit
that referenced
this issue
Jul 8, 2016
Fix problem with Safari inserting line breaks before in-line math. #1478
==> Merged |
dpvc
added a commit
to mathjax/MathJax-test
that referenced
this issue
Aug 18, 2016
==> In testsuite MathMLToDisplay/issue1478.html |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For elements that shrink-wrap their contents (like table cells or inline-block elements), the container width is measured as 0, and so line breaking can't be properly done.
Find a way to get the proper container width in that case (while still handling floating elements and other things that affect the width).
See issue #571, and also #1466.
The text was updated successfully, but these errors were encountered: