[daymi]

This article is kinda weird--it mentions MathML in passing and then spends a large amount of time on MathJax etc.

The correct fix is to have MathML natively on all browsers (no JS)--and Igalia is working on that: https://mathml.igalia.com/faq/

[jfim]

The worst part about the MathML debacle is that it actually used to work in Chrome a decade ago or so, but then it got removed because there was no real support for maintaining it within the Chrome team.

[bariumbitmap]

Yes, it's been almost eight years since Chrome removed their MathML support. The rationale at the time was unspecified security and performance problems:

https://www.cnet.com/news/google-subtracts-mathml-from-chrom...

A developer who worked on it, David Barton, had this to say in 2015:

> I volunteered for a year and got MathML working in Chrome 24, but Google turned it off in Chrome 25 because I couldn't afford to keep maintaining it for free. (Yes, grumble. Donate your nickels to Google.) There was a security bug, but Google had a fix, which has since been landed in WebKit and the Safari browser, for instance. No one on the Chrome/Blink team cared about MathML, so they preferred removing it to maintaining it. They tell people that a library like MathJax is good enough, but it isn't without native browser support for MathML - it's too slow for many use cases, it doesn't integrate well enough with CSS, etc. (the MathJax team agrees with all this). Presumably as digital textbooks gain in popularity, Google will rethink their position, or schools will have to use a different browser than Chrome (Firefox and Safari would both work). In the meantime, Google has no one working on MathML in Chrome at all, even part-time. Go figure. (And no, I would not work on it again.)

https://www.quora.com/Why-did-Chrome-drop-MathML-support?sha...

There's also a chromium bug report from 2009:

https://bugs.chromium.org/p/chromium/issues/detail?id=6606

and a WebKit bug from 2005:

https://bugs.webkit.org/show_bug.cgi?id=3251

[claudiawerner]

The Chromebook team at Google also removed the Japanese-input Dvorak layout on Chromebooks. I updated one day and the option just didn't exist any more - and I know I wasn't the only user. It's very frustrating, and I had to use some X11 shim commands to get around it until I ditched the Chromebook.

[chaoticsystem]

I agree. There mainly 3 options to render math

1- You either use a JS library (MAthJax) 2- Use PNGs or vector graphics (there are tools for that) 3- Use MthML which only works well in Firefox.

Clearly fixing the issue in #3 brings the most benefits.