Last modified: 2014-06-10 11:53:19 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 7756 - multi-resolution image viewer
multi-resolution image viewer
Status: NEW
Product: MediaWiki
Classification: Unclassified
File management (Other open bugs)
All All
: Low enhancement with 2 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
Blocks: Wikisource
  Show dependency treegraph
Reported: 2006-10-30 10:38 UTC by David Monniaux
Modified: 2014-06-10 11:53 UTC (History)
5 users (show)

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


Description David Monniaux 2006-10-30 10:38:52 UTC
With projects such as Wikisource, and activities such as the German chapter's
digitizing of old manuscripts, we're going to get an increased number of very
large images (high-resolution scans of whole pages).

Currently, such images are shown as thumbnails in the image description size,
and if one wants to see details, one has to load the whole image into the
browser. This is not very user-friendly, especially for people with slow

I suggest we do a multi-resolution image viewer like the one on

It allows the user to navigate inside the image at different resolutions, only
loading the parts that are actually needed.
Comment 1 John Mark Vandenberg 2011-03-26 05:02:57 UTC
A lot of this functionality is now available in

A lot of it is implemented in JavaScript, so it might be possible to demo it on Commons.  Ideally this should be rolled into core.

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