User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20060918 Minefield/3.0a1 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20060918 Minefield/3.0a1 gradients inside svg:symbol aren't rendered. gradients outside svg:symbol are rendered. Reproducible: Always Steps to Reproduce: 1.Open a svg file which has gradient(s) inside svg:symbol aren't rendered. 2. 3. Actual Results: gradient(s) are not rendered. Expected Results: gradient(s) are rendered.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060920 Minefield/3.0a1 Confirmed.
Why would you put the gradient _inside_ the symbol? The elements in the symbol are probably cloned into a shadow tree, in which case you're increasing memory use (and there are going to be multiple shadow elements with the same ID).
(In reply to comment #3) > Why would you put the gradient _inside_ the symbol? Adobe Illustrator 12.0.1, SVG Export Plug-In exports svg files which include the gradient inside the symbol. For example, http://spreadfirefox.jp/foxkeh/downloads/parts/tail01.svg another examples at http://spreadfirefox.jp/foxkeh/downloads/parts/ # A mascot in those pages is Foxkeh, a mascot of Firefox brought by Mozilla Japan.
#3 jwatt asks "Why would you put the gradient _inside_ the symbol?" one reason is authoring tool user interface. beyond hand coding... ie unless a number of icons are saved as a set at one time, each will have the gradients, then when the icons are agglomerated, there is much duplication: http://www.openicon.org/icon-ark/freedesktop/gnome/devices.svgz
For the SVG-edit project, I'm working on arbitrary SVG importing. The idea is to insert a <symbol> element with the data, so multiple copies can be made using <use>. This bug means that import files with gradients will thus appear filled in black when using Firefox. As a workaround I was going to put the imported <svg> in a <defs>, then have the <use> elements refer to that, but unfortunately Adobe Illustrator incorrectly displays an image like this (it does fine with <symbol>). A bug on their part, certainly, but it forces me to decide whether to support Firefox or Illustrator. Considering how <symbol> is very very similar to <svg> elements (in which this bug does not occur), I find it hard to imagine that this bug would be hard to fix.
Just FYI: The Foxkeh assets, including the broken tail SVG files in comment 4, have been moved to http://www.foxkeh.com/downloads/parts/
Created attachment 574211 [details] Test case with overlapping IDs and hidden groups A similar problem occurs when we have overlapping IDs and the first occurrence is within a hidden group. This crops up in Santa's Workshop and results in the snowflakes, trees and elves appearing partially or wholly black: http://ie.microsoft.com/testdrive/Performance/SantasWorkshop/Default.xhtml The attached test case is a simplified version of what's happening in Santa's Workshop. I suspect the root cause is the same as this bug. Namely, if a gradient first appears in a context that isn't rendered we seem to refuse to render it from there on. The fact that Illustrator is exporting this sort of arrangement raises the importance of this bug as does its use in Santa's Workshop.
The display:none is a different issue, bug 376027 tracks that.
It has now been a year and eight months since the last entry in this log, and seven years (SEVEN YEARS!) since this bug was first reported and still not been fixed. WTF?? I use Illustrator. I create SVG files. Some of those files have symbols in them. And the only browser that can't render them with gradients is Firefox. I don't want a work-around, I don't want a temporary solution: I want to be able to create a symbol with a gradient inside of it and have it render correctly. After seven years, this is too much to ask of Firefox?? Even an outdated version of Internet Explorer can handle this job. But not Firefox. Brilliant. Seven years. Wow. Time to give up and move on to some other browser, I guess.
Kirby, please keep comments to those which help fix the bug. For progress updates, please follow bug 376027. My previous patch for that bug also fixed this bug (since they have the same root cause) but was unfortunately rejected due to questions raised about the validity of the spec. I have investigated an alternative approach and written it out in detail so that another contributor can implement it. If no one else is available I will try to implement it soon.
(In reply to Brian Birtles (:birtles) from comment #14) > Kirby, please keep comments to those which help fix the bug. For progress > updates, please follow bug 376027. My previous patch for that bug also fixed > this bug (since they have the same root cause) but was unfortunately > rejected due to questions raised about the validity of the spec. I have > investigated an alternative approach and written it out in detail so that > another contributor can implement it. If no one else is available I will try > to implement it soon. Brian: I am sorry my previous message came out sounding so angry and frustrated. I wish you the best of luck in finding a solution to this problem— know that I am continuing to monitor it with fingers-crossed.