MathML-Core Support

Open source

Ensures the ongoing implementation, alignment & maintenance of MathML-Core in open source browsers


Become a financial contributor.

Financial Contributions

Recurring contribution


Become a backer for $5.00 per month and support us

Starts at$5 USD / month

Latest activity by

Recurring contribution


Become a sponsor for $100.00 per month and support us

Starts at$100 USD / month

Custom contribution


Make a custom one-time or recurring contribution.

Latest activity by

+ 5

Top financial contributors


Murray Sargent III

$50,000 USD since Jun 2021

Neil Soiffer

$25,000 USD since Jun 2021

Beni Paskin-Cherniavsky

$50 USD since Nov 2021

Deyan Ginev

$40 USD since Sep 2021

Brian Kardell

$20 USD since Aug 2021

Pelle Wessman

$10 USD since Oct 2021

Viktor Mukhachev

$5 USD since Nov 2021


Open Source Collective

$750 USD since Jun 2021

Open Collective

$750 USD since Jun 2021

MathML-Core Support is all of us

Our contributors 11

Thank you for supporting MathML-Core Support.



Murray Sargen...

$50,000 USD

Neil Soiffer

$25,000 USD

Deyan Ginev


$40 USD

Brian Kardell


$20 USD

Even small, recurring donations help support on...

Pelle Wessman


$10 USD


Transparent and open finances.

Today’s balance

$69,110.89 USD

Total raised

$69,110.89 USD

Total disbursed

--.-- USD

Estimated annual budget

$76,656.97 USD


  The need for browsers to natively render mathematical text has been evident from the earliest days of the Web at CERN.  Mathematical notations form a fundamental aspect of writing systems and are found in all civilizations. They have been instrumental throughout history for the diffusion and development of scientific and technical knowledge. MathML, the W3C standard for this, along with SVG, is one of only two other markup languages which are specially accounted for by the HTML specification and the HTML parser and are embeddable in HTML itself
However, MathML has a complex history.  Its support in browsers thusfar has largely been achieved by contributions to the open source projects.  Like SVG, its specifications came from a different (pre-HTML5/WPT) era.  This meant that on the one hand they had a wide ecosystem of some support and tooling outside of browsers, and on the other they lacked important details and rigors explaining how they fit correctly and interoperably into the web platform.  As they lacked interest and involvement from implementer, the gaps between specs and browsers didn't improve.  Eventually the Working Group disbanded. 
In 2018 a group of people came together to attempt to correct this situation.  Driven by implementation support and expertise from Igalia partially supported by some grant investments, there was a new effort to develop support in Chromium and identify a path to put things back on track.  This resulted in a new specification, MathML-Core, which provides the necessary details, a new shared test suite in Web Platform Tests and several changes (including partial support in Chromium behind a flag). 
Perhaps the biggest hurdle for MathML in browsers has always been implementer investment.  While it is very important, the fact that it is a significant feature which is less broadly appealing than many others and was in a complex state always makes it difficult for it to get the priority and attention it needs.  However, relying exclusively on vendors for all development and maintenance investments isn't necessary, or perhaps even advisable.  Just as Open Web Docs established a way to collectively ensure the health of MDN, MathML-Core support aims to establish a collective investment in the commons to fund these activities.  MathML-Core support aims to make sure that MathML-Core has diversified implementation investements for all browsers that aren't subject to the complexities of prioritizing overall browser development budgets or held back by changing financial situations of any one company. 
This collective intends to prioritize funding  by first completing the two main items lacking in the Chromium implementation (tables and stretchy operators). Over the next year following, we will fund the the necessary maintenance and followup work that follows releases, and then continue the work to align implementations and improve interoperability.

Our team