Last modified: 2010-05-15 14:35:57 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 1352 - On image description pages: If the resized image is bigger than the original the original gets displayed.
On image description pages: If the resized image is bigger than the original ...
Product: MediaWiki
Classification: Unclassified
File management (Other open bugs)
All All
: Normal minor (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2005-01-17 19:01 UTC by Colin Pitts
Modified: 2010-05-15 14:35 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Colin Pitts 2005-01-17 19:01:06 UTC

displays the image at full size (1200 x 1398), regardless of user preferences on
size or whether one is logged in or not. The "Download high resolution version"
link appears, even though the image is being displayed at full size.
Comment 1 Daniel Kinzler 2005-01-21 22:53:46 UTC
URLs of images that have this probelm:

the strange thing is that thumbnails of those images work correctly. So, what is
the problem here? Maybe the software does not detect that the image *should* be
scaled. but in that case, the "high resultion" link would not appear, right?

Comment 2 Daniel Kinzler 2005-01-21 23:01:23 UTC
Something else: it appears that the software indeed does not try to scale the
image, or it fails trying: The URL of the supposedly scaled image is the same as
the URL of the "original" version. I.e. no temporary/cached scaled version of
the files is created/used.
Comment 3 Daniel Kinzler 2005-01-22 02:07:05 UTC
JeLuF told me this happens when an image gets bigger (in bytes) when scaled
down. This is the case for images that have a low color-depth (like 4 or 8 bit),
which are rendered in 24 bit depth when scaling (because auf antialiasing),
creating a file bigger than the original. In this case the software does not use
the scaled image, because it would be against the original purpose of this
feature, namely to preserve bandwidth.

However, as this feature is also very useful to allow large images to be seen
"at once" even if the original is bigger than the users screnn, and this is
percived as the main advantage by many users, this is confusing. Also, as images
with a low color-depth are not very frequent, i would argue that enabling
scaling even in cases where the scaled file is bigger than the original would
profit the users and wouldn't hurt too much bandwidth-wise.
Comment 4 Colin Pitts 2005-01-22 03:14:38 UTC
Even if the behavior is left as-is, it needs to be better documented so it
doesn't confuse anyone else in the future.
Comment 5 Andrew Archibald 2005-02-27 09:21:04 UTC
This bug was introduced by an attempted solution to bug 1218.

I suggest two things:

* Always resize images.
* Use ImageMagick's "identify" to count the colors in an image (possibly only if
the input image was indexed or grayscale); if it's 256 or less, convert the PNG
to an indexed PNG (losslessly). 

The first cures the user hassle; the second will probably avoid most of the
cases where the image actually gets bigger (the original motivation for the
unresized images).
Comment 6 Ævar Arnfjörð Bjarmason 2005-04-16 19:03:48 UTC
The behaviour for image resize has been changed in HEAD (and note that this is a
change of behaviour, not a bug as such.)
Comment 7 Ævar Arnfjörð Bjarmason 2005-04-16 19:05:31 UTC
Changed the summary to reflect the issue.

Note You need to log in before you can comment on or make changes to this bug.