private const UNIT_EM = [ 'em' => 1, 'ex' => 0.43, 'pt' => 0.1, 'pc' => 1.2, 'px' => 0.1, 'in' => 7.2, 'cm' => 7.2 / 2.54, 'mm' => 7.2 / 25.4, 'mu' => 1 / 18,
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Yesterday
People chose the amount of space to add by visual inspection using the old renderer. So if the spacing is different, then all of those numbers need to be changed or your are breaking authors' intent.
Can you check side by side with the old server-side SVG mode, to make sure the spacing is actually the same?
I believe the centering is because the final newlines are being ignored.
We don't have visual parity, but it's no longer possible to check.
Sun, Nov 15
Yeah, the new font(s) between Mathjax v.2 -> v.4 have a bunch of pretty questionable changes. It's probably possible to combine the best features of each by making a custom set of fonts, but that would take some amount more effort than just picking one of the provided options.
Sat, Nov 14
You probably want to set it to render in display style by default instead of text style.
Fri, Nov 13
I don't understand why A \mathbin{()} B seems to render correctly now, but A \mathbin{\vert} B and A \mathbin{.} B do not.
Thu, Nov 12
Can you check all of the different units, and compare graphically side-by-side between old and new renderings?
The spacing still does not match the previous "server-side SVG" mode
Wed, Nov 11
Can we get a survey of how many such empty underlines there are on English Wikipedia, and where? Maybe we can manually go change them. The "client-side SVG" mode is still inconsistent with "server-side SVG" mode, but it now matches the behavior of LaTeX.
Tue, Nov 10
And one other very weird thing: C'^{*\!} and C' render completely inconsistent prime symbols:
Also, a related problem, \prime by itself should not render as a superscript.
Mon, Nov 9
Here's another example:
You may want to check stuff like the very simple {{} - x}, which should make - a binary operation but currently does not.
You should start by making the output consistent with the "server-side SVG" mode to fix the many articles which the new rendering mode broke ASAP.
Sun, Nov 8
A newly found very serious issue reported by Wikipedians: mathematical notation contained in footnotes is sometimes not appearing at all in the mouse-hover popup footnote boxes (though it does appear in the footnote as rendered at the bottom of the page).
Why don't you set that up. That is a completely ridiculous thing to expect every Wikipedia author who wants to see how the old rendering mode worked to do.
@Krinkle Can you please ASAP give us a way to (1) see a particular expression as it renders in "server-side SVG" mode, and (2) give us a way to see an entire English Wikipedia article rendered using the "server-side SVG" mode?
Sat, Nov 7
@Krinkle Your page shows an empty image. When I click it, the URL is
Fri, Nov 6
Did you also address the issue with a trailing {} at the end of a multi-line environment?
since they should be replaced with a single math tag
Or, much more reasonably, it could easily be kept working in English Wikipedia for the next several months.
As an example:
This rollout is totally and utterly fucked. It is impossible to overstate how incompetently this is being done.
Thu, Nov 5
You are not convinced that {} should be treated as explicit (empty) content? Why?
Wed, Nov 4
By the way, the "mathmode=mathjax" and "mathmode=mathml" URL options seem to be broken, which is preventing Wikipedians from assessing the new rendering mode.
I think the complaint from row 60 (0.{\underbrace{999_\ldots}_H}) was about the spacing before the underbrace group, i.e. the awkward spacing "0. 999" rather than the internal spacing inside the underbrace.
This should be high priority. This is a really bad bug.
{} needs to act as an empty placeholder in every context, and some nontrivial amount of testing needs to be done to make sure the behavior is the same as LaTeX in all sorts of nesting contexts.
Tue, Nov 3
Can you please either revert this deployment or fix (1) the horizontal whitespace gobbling bug and (2) the broken align whitespace bug(s) ASAP? These bugs are critically bad.
Sun, Nov 1
This should probably be reopened. The prime symbols are still too far from the letters. But if a subscript is included, it gets comically bad. Example: \psi_n''. Expected rendering on the left, "client-side SVG" mode on the right:
Okay, but your screenshot doesn't actually show a resolution of the issue as stated in the ticket report here.
Sat, Oct 31
I'm assuming that the top screenshot example is the current "server-side SVG" mode, and the third image example is the upcoming "client-side SVG" mode? These are clearly different fonts being used.
I don't understand why this is closed when your screenshot shows a clear difference.
You wrote;
Positions 62 and 225, \mathcal: drawn as script letters. Our MathML uses U+1D49C and up, while mathjax-tex has the calligraphic glyphs only at A–Z.
Fri, Oct 30
@Krinkle Why is this triaged as "low priority"? Having bold Greek letters italicized against authors' intent can potentially change the meaning of the symbols and make them technically incorrect. This is the kind of thing that according to the current criteria is a "broken (high priority)" bug.
Thu, Oct 29
Can you see how "we're shipping this in 4 days irrespective of any complaints or objections, after substantially ignoring many concrete criticisms over the past few months" does not really seem like a good faith collaborative effort? Especially since it comes after a string of similar short-deadline ultimatums that never involved any kind of apology, reset, or promise to do better. Basically, you have pre-decided to steamroll us, with indifference to severe quality problems and to Wikipedia authors and readers. For a volunteer project, it feels profoundly disrespectful.
Here, concretely, is a partial list of bugs which in my opinion must all be fixed before deployment is reasonable.
{{Q(√5)}} expands to {{tmath|\Q\bigl(\sqrt5\;\!\bigr)}}, with 2 math units space added after the radical sign because otherwise it nearly collides with the closing paren. Formerly this was using ~\! which added only 1 math unit of space, but ~ doesn't work the same in client-side SVG mode.
Here are a bunch of the remaining bugs all in one place:
I agree this single-character overline bug is not the most serious or urgent. I wouldn't demand blocking deployment conditional on fixing this, though I would also like to see it fixed relatively promptly.
Wed, Oct 28
Can we have some time (like, at least weeks) after the proposed version is considered ready enough by WMF / Mediawiki developers before deployment, to give time for additional bug surfacing, testing, checking pages, discussion, etc.? And ideally, some concrete discussion about what kind of bugs remain, how feasible they are to fix and how much effort that will take, etc.?
To add a positive note here:
That page is an unsorted list of miscellaneous reported issues, not a discussion.
Why is this marked "resolved"? The current state is still moderately broken.
It seems like the version inside fractions is maybe fixed? But a sums in a square roots with \textstyle set is still the wrong size.
There are also still severe bugs that you haven't even yet made issue reports for, all these months later. You are still months of work away from a state that can be shipped without fundamentally breaking the encyclopedia.
In T271001#12484145, @MSantos wrote:TL;DR; the confidence to proceed with the roll-out is high and we have performed thorough analysis to support that.
Sun, Oct 25
@Aklapper Nobody knows what "Award Token" means.
Mon, Oct 19
Even if every existing expression in Wikipedia is made to work by some combination of workarounds or conditional checks or whatever, if the behavior is different at a fundamental level, that seems like a significant problem, since future arbitrary combinations of nested content may behave differently from LaTeX in ways that make no sense to authors.
Sun, Oct 18
Can we figure out how to make a custom font where the AMSFonts \mathcal letters have been moved to the script character code points?
Oct 15 2026
Can this space be made as precisely as possible the same as the current behavior of the "server-side SVG" mode? Your proposed fix still seems wider.
Oct 14 2026
Comparing against pdflatex and stock MathJax 4.1.3 showed that most of them are not in our code at all, but in the mathjax-newcm font
@MSantos How important bugs are also depends on how often behavior is relied on, how important the relevant features are to the pages that use them, etc.
Oct 6 2026
Thanks @Physikerwelt for making this issue. I don't have a complete understanding of what symbol coverage these various fonts have, what fallback font(s) would be used for symbols not found in the chosen font, etc.
I think this is a nontrivial accessibility issue. I'm concerned that some readers will have difficulty reading mathematical expressions if the smallest symbols get too thin.
Oct 5 2026
The issue here goes far beyond the bug tracker. The problem is a fundamentally broken high-level process, almost total lack of communication, and completely unprofessional project management.
Or, for completeness, here is the full range of font sizes in LaTeX from \tiny to \Huge, rescaled to the same absolute size:
The letters are not smaller overall. The issue is that the strokes are very thin.
Oct 3 2026
\nleqslant and \ngeqslant were just examples. There are a number of other affected symbols (i.e. symbols which do not render correctly in "client-side SVG" mode), beyond just the ones explicitly reported.
Sep 30 2026
Can whoever fixes this also make sure that the problem is fixed at a fundamental level? I imagine there are probably other combinations of nested stuff that lead to the same outcome, but I didn't exhaustively test every imaginable combination.
Sep 29 2026
You still haven't bothered to ask Wikipedians what issues they consider essential to fix, and you still haven't even triaged all of the reported issues.
Sep 28 2026
The image included with this bug report doesn't appear.
Adding commands such as those found in the scalerel package is definitely intended as a separate feature request, not part of a bug report.
And also one about the issue of spacing getting really wonky in various contexts such as under overlines/overbraces and in fractions involving exponents?
Thanks, @MSantos, for adding a bunch of new tracker tickets.
The fundamental issue (which affects all versions of MathJax) is that there is no change of font for different sizes of symbols, so the same outlines are used irrespective of symbol size. In LaTeX running offline, different sizes of symbols use different outlines, which have had their shapes modified to suit the size. Symbols intended for small size rendering often have thicker strokes, simplified features, larger counters (spaces inside a letter), modified x-height, etc.
Sep 23 2026
There are enough extant examples of \dots – and enough people are going to keep making more, even if the existing ones were somehow all changed – that I don't think it's reasonable to break this command, which authors expect to work.
Sep 21 2026
Here's what their website says:
I'm not too worried about permalinks.
Sep 18 2026
In the current "server-side SVG" mode, px and pt behave exactly the same.
Make sure that if "server-side SVG" and "client-side SVG" are rendered side by side, the appearance is the same. For some reason the two versions in your "after" screengrab seem to have different font sizes, so it's hard to tell.
Sep 17 2026
The units advertised by https://en.wikipedia.org/wiki/Help:Displaying_a_formula are:
em, mu, ex, in, pc, pt, cm, mm
could be argued that is syntax we do not support
Sep 16 2026
There are many more critical problems that should block deployment to not break many, many Wikipedia articles. Many of them haven't been given bug reports here yet, but you can see a list of reported issues at https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Mathematics/MathFormattingBugs
The best way to fix these issues would be to make sure to use the fonts from AMSFonts / AMSSymb for mathematical symbols. These are what Wikipedia has always used in the past, are used by the vast majority of LaTeX documents, and are what authors expect.
Is this related to the strange client-side SVG issue where two completely different types of prime symbols are used in: C'^{*\!}, C'?
This is all rendered with MathML? Yeesh, none of those looks amazing, and most of them are awful. If that's the current state, MathML doesn't seem ready for serious use.
Sep 15 2026
If we want things to work as authors expect, and we want to get something adequate in the relatively short term, we should start by trying to use a version of Computer Modern for the letters, numbers, and basic math symbols, and the font from AMSFonts (which is intended for use with Computer Modern) for other math symbols.
The behavior of an explicit command like mathop, mathrel, etc. should not depend on the font at all. We should be turning whatever is contained in such commands into some kind of symbolic unit, and then setting the space around that based on which command it was.
Sep 14 2026
In my opinion, we should use the font from the amsfonts/amssymb package for all of the usual mathematical symbols, at least for the "client-side SVG" mode. This is what authors expect, what Wikipedia has always used in the past, and these fonts are freely available.
In LaTeX, the colon made by ":" is supposed to be a "mathematical relation" symbol. The spacing before and after must be the same as for other mathematical relation symbols like =, >, ≥, or →. This is subtly different than the spacing used for binary operation symbols like +, −, ·, or ×. The two types (mathrel vs. mathbin) also behave differently in different contexts.
Is there a version of this bug relevant to the "client-side SVG" mode? That seems like the more important one to address in the short term.
Sep 9 2026
That one is marked as "resolved"; it looks like just matrices were special cased, and the underlying issue affecting all multi-line environments was not really addressed.
Trailing line breaks need to be ignored in every multi-line environment (align, alignat, array, cases, etc.).
The font size for math should be the same as the font size for adjacent text. Bumping the font size for all math is a terrible idea.
It doesn't matter what is causing the bug. This blocks deployment.
A few of the ones that must be fixed to avoid breaking many, many Wikipedia articles:
The horizontal length is about right, but the horizontal position is wrong. (The vertical position is also wrong.)
This seems to be an intentional change in upstream MathJax
Instead of bumping the deploy 1 week at a time every time it is a few days away, from one absurdly unrealistic date to a different equally absurdly unrealistic date, how about you work with Wikipedians to figure out which bugs are completely unacceptable, which ones need discussion, etc., and then put up some more plausible milestones that development needs to achieve?
Sep 8 2026
All of the units {em, mu, ex, in, pc, pt, cm, mm} need to be supported and behave the same way between "client-side SVG" and "server-side SVG" mode, from all of the align-type environments (including also cases, matrix, etc.)
\overline{\alpha} is still incorrect in "client-side SVG" mode. It renders too close to the letter and is not properly horizontally aligned. (This should maybe be recorded as a different ticket.)
Sep 3 2026
Here's what this looks like when rendered with LaTeX, using usual defaults:
I think it would be a somewhat okay size if we used a dedicated font for the smaller text. in the new default font for "client-side SVG" mode, which is already on the thin side for regular size, anything this small starts getting extremely thin, to the point it's hard to read