Last modified: 2008-10-14 04:38:30 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 5108 - SVG: attributes not inherited from root svg element
SVG: attributes not inherited from root svg element
Product: MediaWiki
Classification: Unclassified
File management (Other open bugs)
PC Linux
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
Blocks: svg
  Show dependency treegraph
Reported: 2006-02-26 23:30 UTC by Martin von Gagern
Modified: 2008-10-14 04:38 UTC (History)
1 user (show)

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


Description Martin von Gagern 2006-02-26 23:30:39 UTC
I have a SVG file with fill="none" specified in the root <svg ...> element. With
this setting, polygons are filled black by the WikieMedia engine. When I repeat
the attribute in the containing <g ...> group, the polygon is correctly just
stroked and not filled. The same is true for stroke width; it is inherited from
parent <g ...> elements but not from the root <svg ...> element.

On the URL which I supplied, the first version I uploaded is rendered black, the
second one rendered transparent. In the third version I moved the width
specification as well, which fixed that problem as well.
Comment 1 Brion Vibber 2006-02-27 02:31:14 UTC
Still renders solid in librsvg 2.14.0.

Bug filed upstream:
Comment 2 Tim Starling 2008-10-14 04:38:30 UTC
Fixed now that we have upgraded to librsvg 2.22.0. 

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