Slashdot videos: Now with more Slashdot!

View

Discuss

Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

How would text rendering be a problem for the browser? I'm assuming that Mac OS X isn't written by complete idiots, and that non-"retinal" apps get upscaled with proper high-DPI text rendering, meaning that the only thing Firefox has to deal with is scaling images.

This is true, right? Apple wouldn't do something completely stupid like require all apps that want to do "retinal" be completely rewritten to deal with that, would they?

I suppose they would, wouldn't they.

In any case, text rendering is a thing that the OS should be dealing with, not the app, so it shouldn't be a Firefox problem. All Firefox should need to do is provide higher-res images. Which basically don't exist on the vast majority of sites, so they might as well not bother on something that maybe a percent of a percent of users would be able to use.

What I find more fascinating in TFA is that Firefox has added simple support for HTML5 Sandboxes. You can apparently specify whether the data inside the IFRAME is allowed to access outside domains, etc. (if I am reading it correctly; I am not actively involved in web design at the moment and so am a bit behind the curve; does anyone know how good this sandbox function is compared to other software/browsers?).