The MathJax team is pleased to announce version 3.1 of MathJax, released earlier today. This is a feature release that includes a number of API improvements, new extensions, and updates to the assistive tools, as described below. It also includes several bug fixes.
See the individual issues and pull requests linked below, as well as the What’s new in v3.1section of the MathJax documentation, for more details.
Also note that the demos in the node examples have been updated and expanded to include examples of using a simplified interface for MathJax in server-side node applications, MathJax with Puppeteer, and MathJax with jsdom.
textmacros
extension for handling some macros in text-mode. (#509)safe
extension and component. (#514)noundefined
extension. (#507)mtextInheritFont
, and provide new mtextFont
option. (mathjax/MathJax#2189)formatError
a configuration option for tex input jax. (#483)startup.promise
so it is always valid. (mathjax/MathJax#2307)data-mjx-error
, similar to compile/typeset errors. (#490)bbox
property. (#495)output/common/BBox.ts
to util directory. (#494)output/common/CssStyles.ts
to util/StyleList.ts
. (#493)scriptminsize
and scriptsizemultiplier
. (#515)texClass
for multi-character <mi>
elements. (#503)node-main
to be able to load SRE more easily. (#479)texClass
. (#512)classList
when elements don’t have it. (mathjax/MathJax#2411)\underset
explicitly turn off movablelimits. (mathjax/MathJax#2460)\boldsymbol\partial
work properly. (mathjax/MathJax#2417)\overbrace
in SVG output. (mathjax/MathJax#2402)Although version 3.1.0 was released earlier today, it may take a day or two for the new version to propagate to the various CDN network computers, so you may not see v3.1.0 immediately if you are loading mathjax using a generic mathjax@2
URL. You should be able to obtain it immediately if you use the full version mat...@3.1.0
.
You may also have a cached version in your browser, so may need to either clear the browser cache, or relaunch your browser (or both) in order to get the latest version (the cached version should expire in about a week, depending on the CDN being used).
Note that it is possible for some files to be updated before others, so it may be the case that users of websites that load extensions (either explicitly or by autoloading TeX packages) may get mixed versions for until the CDN versions stabilize, which should be within a day. If you are loading one of the combined components (e.g., tex-chml.js
), this is less likely to be an issue, and if you are loading a component ending in -full
it is even less likely to occur.
Version 3.1.0 is available immediately from npm and GitHub for use in node applications.