# Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 72240 - Remove PNG only rendering mode
 Summary: Remove PNG only rendering mode
 Status: Product: NEW MediaWiki extensions Unclassified Component: Math (Other open bugs) unspecified All All Unprioritized normal (vote) --- Nobody - You can work on this! 69702 28258 Show dependency tree / graph

 Reported: 2014-10-19 17:59 UTC by physikerwelt 2014-10-27 16:09 UTC (History) 3 users (show) gwicke peter.krautzberger physik --- --- ---

Attachments

 physikerwelt 2014-10-19 17:59:31 UTC To be more flexible with new features the PNG only rendering mode should be deprecated and finally be removed. Peter Krautzberger 2014-10-24 10:18:00 UTC +1 for that. But http://www.mediawiki.org/wiki/Compatibility lists IE8 and Android 2.3 as Grade A (neither of which supports SVG or MathML). physikerwelt 2014-10-24 10:24:51 UTC Yes.I think we should continue to support png images for now. That's described in 69702 Gabriel Wicke 2014-10-27 16:09:53 UTC We should support PNG fall-backs in the MathML mode as well, so that we can eventually make that the default mode for anonymous users. By rendering the PNGs from SVGs we should be able to reuse the baseline and size information provided by MathJax, which in turn should let us scale the fall-back the same way we do with SVGs. The quality of scaled images might not be perfect, but it'll remove the inconsistency in size with associated work-arounds like \scriptstyle.

 Note You need to log in before you can comment on or make changes to this bug.