Last modified: 2012-07-23 12:22:17 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T40508, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 38508 - SVG thumbnails should not be rasterized
SVG thumbnails should not be rasterized
Status: RESOLVED DUPLICATE of bug 3593
Product: MediaWiki
Classification: Unclassified
File management (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-07-19 21:35 UTC by andybaumgar
Modified: 2012-07-23 12:22 UTC (History)
6 users (show)

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


Attachments

Description andybaumgar 2012-07-19 21:35:37 UTC
SVG is supported in most modern browsers.  The rasterization method used for svg's in mediawiki is unnecessary and lower quality that simply scaling the svg size.

Please add support for native svg and thumbnails.
Comment 1 Smallman 2012-07-22 23:57:01 UTC
There are certain security considerations that have to be taken into account such as what to do with <image> tags pointing to external images.
Comment 2 andybaumgar 2012-07-23 00:10:36 UTC
Hi, I agree there could be security risks.  Maybe native svg could be added as an option with a warning like raw HTML.  This way users with internal wiki's not as concerned with security could take advantage of browser svg rendering while svg security catches up.
Comment 3 Bawolff (Brian Wolff) 2012-07-23 12:22:17 UTC
(In reply to comment #2)
> Hi, I agree there could be security risks.  Maybe native svg could be added as
> an option with a warning like raw HTML.  This way users with internal wiki's
> not as concerned with security could take advantage of browser svg rendering
> while svg security catches up.

I imagine if we did this, we would address the security issues first (Well they do exist, they're not exactly impossible to deal with). I imagine its mostly public wikis who would want this feature. More pressing concerns is having fallbacks for browsers that don't support it, how different browsers render svgs differently, etc.

*** This bug has been marked as a duplicate of bug 3593 ***

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


Navigation
Links