Last modified: 2014-02-12 23:45:59 UTC
Created attachment 9333 [details] Screenshot on Nexus 1, Android 2.3.6, Android stock browser Same basic issue as bug 32095 which covers MobileFrontend-specific UI elements. Thumbnail images, math renderings, etc get used at resolutions matching CSS pixels, which traditionally matches physical screen pixels on desktop browsers and many older phones. Many newer phones have higher-resolution displays: iPhone 4's 320dpi Retina display; 240dpi "hdpi" on many Android phones including the Droid, Nexus 1 and Nexus S, and the upcoming Nexus Galaxy will also have a 320dpi-ish display. This causes the images to be upsampled, showing either blurry or blocky, and is particularly noticeable for diagrams with clean lines and math equations which are meant to look as good as surrounding text. CSS media queries can be used to get the display resolution -- you WILL NOT be able to reliably guess that on the server side from User-Agent data --
Created attachment 9334 [details] Screenshot in iOS 5 simulator set to iPhone w/ Retina display
Replacing dep on bug 32697 (use high-res raster images for math) with use of MathJax (bug 31406). It renders lovely on Android & iPhone browsers that have the high-res stuff.
Is this still relevant? It's almost a year old..
Still relevant, not much has changed in the situation other than more phones are shipping with higher-resolution screens, and some laptops are as well. MathJax is enabled as a user option for math, but probably doesn't work in MobileFrontend and since it's not the default it doesn't reach typical readers anyway. Other content images are still served at 1.0x resolution and appear blurry on high-res screens.
Let's merge this in with bug 36198 though, and not worry about math just now. *** This bug has been marked as a duplicate of bug 36198 ***
