Last modified: 2012-10-31 15:11:09 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 T21224, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 19224 - SVG rendering: problems with paths beyond page extent
SVG rendering: problems with paths beyond page extent
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
File management (Other open bugs)
unspecified
All All
: Normal minor (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: svg
  Show dependency treegraph
 
Reported: 2009-06-15 18:38 UTC by Alexander Karnstedt
Modified: 2012-10-31 15:11 UTC (History)
3 users (show)

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


Attachments

Description Alexander Karnstedt 2009-06-15 18:38:32 UTC
I've seen that problem on various SVG files, e.g. here: http://commons.wikimedia.org/wiki/File:Hilfe_Geotools_Beispiel_3.svg

If a closed path goes beyond the limits of the SVG page size, there will be strange line artefacts crosswise the PNG file.
Comment 1 Brion Vibber 2009-08-03 16:53:54 UTC
Assigning SVG bugs to Ariel -- need a cleanup pass to see what's fixed up by a librsvg upgrade, what can be resolved with fixes to our font configuration, what can be fixed on our end, and what still needs to be pushed upstream.
Comment 2 Ariel T. Glenn 2011-09-18 09:28:40 UTC
giving SVG bugs back to the pool.
Comment 3 Derk-Jan Hartman 2011-12-04 13:01:40 UTC
It seems the behavior of this image has changed since the last rsvg update. The paths (that are outside of the canvas) are now apparently invalidated and not rendered at all.
Comment 4 Derk-Jan Hartman 2012-10-26 09:36:01 UTC
This problem is now fixed. The linked image now renders correctly.

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


Navigation
Links