3 ms·
It's pixel-doubled like every other non-native-Retina app on your Mac. Why is it Firefox's problem if Apple didn't bother to go to the trouble of making non-Ret
by kevingadd 14y ago
It's pixel-doubled like every other non-native-Retina app on your Mac. Why is it Firefox's problem if Apple didn't bother to go to the trouble of making non-Retina applications readable on a Retina display? The fact that they don't even bother to do filtering when pixel doubling is probably a big contributor to readability issues (note that Vista and W7 do filtering when doing DPI adjustment, likely for this exact reason), not to mention the fact that it appears to be doing subpixel antialiasing when there are no subpixels to address (WTF, Apple?)
- masklinn 14y ago> Why is it Firefox's problem if Apple didn't bother to go to the trouble of making non-Retina applications readable on a Retina display? I'm not sure what they could have done beyond making sure Cocoa's text-rendering routines produce the right "retina" output. Which they do. Firefox (and Chrome) do their own text rendering and rasterizing, as far as OSX can see it they give it a big image to display. Not much OSX can do with that.
- asadotzler 14y agothey could have not pixel doubled the applications and instead let them be smaller and still crisp.
- masklinn 14y agoCrisp is not very useful when you can't read the text or view the pictures because they're a quarter of their "intended" physical size.