Last modified: 2014-10-27 16:09:53 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T74240, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 72240 - Remove PNG only rendering mode
Remove PNG only rendering mode
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Math (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on: 69702
Blocks: 28258
  Show dependency treegraph
 
Reported: 2014-10-19 17:59 UTC by physikerwelt
Modified: 2014-10-27 16:09 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description 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.
Comment 1 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).
Comment 2 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
Comment 3 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.


Navigation
Links