Last modified: 2006-02-11 08:48:36 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 3828 - MediaWiki shouldn't scale SVGs larger than say 2000px
MediaWiki shouldn't scale SVGs larger than say 2000px
Product: MediaWiki
Classification: Unclassified
File management (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2005-10-29 20:45 UTC by David Benbennick
Modified: 2006-02-11 08:48 UTC (History)
0 users

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


Description David Benbennick 2005-10-29 20:45:18 UTC
Currently, MediaWiki will produce a thumbnail of an SVG file up to the larger of
1024px or the "natural size" of the SVG.  This is sort of a security hole, since
SVG files can have arbitrarily large "natural size" without affecting the file
size at all.  See, for example,
[[Image:Map of Colorado counties, blank.svg]].

I propose there should be a maximum thumbnail size for SVG files; say 2000px or
so.  Wikimedia projects certainly never need images larger than this.  Then code
like [[Image:Foo.svg]] with no size specification would use the 2000px
thumbnail, instead of trying to make a gigantic thumbnail at the "natural size".
Comment 1 David Benbennick 2006-02-11 08:48:36 UTC
This issue has apparently been fixed.  Now MediaWiki doesn't scale SVG above
1024px regardless of the "natural size".

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