| Debenben | |
| May 15 2018, 2:50 PM |
| F18280545: IMG_8725.JPG | |
| May 15 2018, 2:50 PM |
| F18280554: IMG_8723.JPG | |
| May 15 2018, 2:50 PM |
When it is not possible to render the equations
the source code should be shown, which, at least for mathematicians is also perfectly readable. Preferably the original LaTeX source code as written by the Wikipedia-editor, not what texvc derives from it.
@Debenben a couple of questions.
@Pkra You are right, it is kernel version 2.6.29 and android version 2.1 update 1. The application is the native Android browser.
Thanks. A first guess would be that SVGs are used instead of PNGs (which would be required for that browser).
Next step. Can you open one of the equation images and check if it's an SVG? (E.g. the URL will include "svg" in the path or you could paste it here.)
When I click it in the android browser it does not open anything and I also can't copy it. I guess it should be click-able though, because the question-mark-icon slightly changes appearance when clicked. I don't know how I can debug it on that device, the browser doesn't give any useful options.
Thanks, @debenden. That's too bad. I couldn't get an old android simulator to work to test it myself.
Maybe someone from WMF could tell which browsers still get PNGs; ping @mobrovac.
If it's indeed the case that SVGs are deliverd instead of PNGs, then the next question seems to be whether MediaWiki supports this version of the Android browser. According to https://www.mediawiki.org/wiki/Compatibility#Browser_support_matrix "Android 2+" is listed with "basic support" which in turn includes "image formats used by the content"; so maybe that's in scope.
What I can do is:
and get an acceptable rendering of those formulas which also works if I switch back to mobile view.
However then (since the equations don't wrap around like on math.stackexchange) larger display equations get cut-off on the right. In the mobile view I can only zoom out until they become unreadable and not scroll horizontally like in the desktop view. I would already be happy if it would just fall back to printing the source code without me having to login or change any settings.
Thanks, @Debenben. I'd suggest first to track down the issue and then think about mitigation strategies (temporary or otherwise).
(But if you need a workaround right away, there's this trick using custom scripts.)
This looks like an issue for the Mobile Frontend folks, so tagging as such.
The default is MathML with SVG fallback for all domains. Additionally, there is a client-side feature check for SVG which should kick in in this instance, but it doesn't.
They're using SVGs e.g. https://wikimedia.org/api/rest_v1/media/math/render/svg/e32110fbce4646ee22f018ae3e27902aa708badd and Android 2 does not support SVG.
We only support Android 2 in a basic support mode (https://www.mediawiki.org/wiki/Compatibility). To fix this, the Math extension would need to use a combination of srcset and png fallbacks for all Math equations. Is that possible from the services side?
@Jdlrobson PNGs are generated, eg., https://wikimedia.org/api/rest_v1/media/math/render/png/e32110fbce4646ee22f018ae3e27902aa708badd.
As @mobrovac mentioned, the modernizr-like check that's in place seems to fail (or perhaps there's an earlier failure).
That's because no JavaScript runs at all in Android 2 so this code won't get executed. The change would need to be in the HTML markup for this to work (e.g. an onerror attribute - https://www.sarasoueidan.com/blog/svg-picture/)
That's because no JavaScript runs at all in Android 2 so this code won't get executed.
Ah, that would explain it ;-)
The change would need to be in the HTML markup for this to work (e.g. an onerror attribute - https://www.sarasoueidan.com/blog/svg-picture/)
Great. If the onerror approach is ok, that seems straight forward.
I haven't read up on all the context (sorry), but from a quick glance, it looks like it might make sense to default to using PNGs in the basic HTML response from the server. Also, to provide SVGs to newer browsers and for optimum high-resolution rendering, it might be possible to use the srcset attribute for the SVG url. Android 2 is old enough that it doesn't support srcset. This has the benefit of not requiring inline JavaScript event attributes and working in a wider set of environments (search-engine scraping, static HTML, Parsoid, VisualEditor), and probably resulting in simpler and easier to maintain code (given pure HTML without embedded JavaScript).