Move mml3 filter to an mmlFilter so that forceReparse isn't needed. (mathjax/MathJax#2718) #765
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR move the MML3 filter from being a
preFilter
to being anmmlFilter
. That way it will always run and you don' have to specifyforceReparse: true
. It also means that (in the browser) you don't have to serialize the math and then re-parse it, as is currently done, since the browser's XSLT parser can work on any DOM fragment. The node version must serialize and re-parse, however.There is a new
enableMml3
configuration option that controls whether the filter is added or not (so that if the extension is packaged with a combined configuration, it can be disabled).This also make the
mmlFilters
public, as it should have been originally.Resolves issue mathjax/MathJax#2718.