MozillaZine

Automatic Image Resizing Checked In

Sunday January 19th, 2003

David Illsley writes: "Yesterday saw the checkin of automatic image resizing (bug 73322) to the Mozilla trunk. When turned on (it's disabled by default) it shrinks any image that is bigger than the window to make the whole image visible. When this is done, the cursor over the image changes to tell you that if you click, the image is restored to full size. You get the best of both worlds! This currently doesn't have a prefs UI in Phoenix but if you put the appropriate pref in you user.js file, it works just fine. This is one of the few features in IE that I have seen and liked and it's great that Moz now has it too. Thanks guys."

To enable this feature in Mozilla, go to Edit > Preferences > Appearance and check the 'Enable automatic image resizing' box. If you're using Phoenix, add the following line to your prefs.js or user.js file:

user_pref("browser.enable_automatic_image_resizing", true);

Phoenix Help has more information about editing Phoenix configuration files.


#58 Re: Re: Nearest Neigbour

by egoots

Tuesday January 21st, 2003 1:49 PM

You are replying to this message

> And although it's a lot more CPU than resizing, I don't think (linear) resampling need be all that slow. Certainly given it would only be used for full-screen image viewing where the > image had been shrunk, I don't see it causing a huge difficulty. Again, you can have thresholds for this so that it is turned off on slow machines.

bilinear interpolation (or higher order interpolations) will be measurably slower than nearest neighbour UNLESS it is done in hardware. Someone pointed out (<http://bugzilla.mozilla.org/show_bug.cgi?id=98971>) that it can be up to 1 or 2 orders of magnitude slower. Also, many more images than one would expect tend to get "scaled" in the browser.

The current view in the relevant bug is that certain people dont want prefs, or "thresholds" or whatever...

It will be interesting to see how this progresses.