https://stackoverflow.com/questions/33087256/how-to-gradient... A developer running in to problems trying to use this
It feels really strange to see this known issue go unaddressed for such a long period since Chromium is the current market leader.
SVG Chromium bug is more than 10 years old
21–30 of 60 posts
Re: SVG Chromium bug is more than 10 years old
#22https://bugs.chromium.org/p/chromium/issues/detail?id=130573...
Vector GPU Rasterization in Chrome is still broken on Apple Silicon Macs. Has been for more than a year.
Re: SVG Chromium bug is more than 10 years old
#23Writing negative replies on bugs like this isn't constructive (like #c89). Browser engineers have an extremely difficult job. The codebase is incredibly complex (they aren't just copying data from one system to another - it takes years to get up to speed in just a small area of the codebase) - any change (even improvements/fixes) risks breaking websites. You might think you are complaining to a faceless organization,…
fs is a legend
Re: SVG Chromium bug is more than 10 years old
#24And???
Sometimes a bug just doesn't have the same importance to the maintainers as it does to you.
If it's that important, fix it yourself.
Re: SVG Chromium bug is more than 10 years old
#25Writing negative replies on bugs like this isn't constructive (like #c89). Browser engineers have an extremely difficult job. The codebase is incredibly complex (they aren't just copying data from one system to another - it takes years to get up to speed in just a small area of the codebase) - any change (even improvements/fixes) risks breaking websites. You might think you are complaining to a faceless organization,…
FS also co-authored the pre-chromium (presto) SVG engine in Opera so he probably has a unique perspective.
Re: SVG Chromium bug is more than 10 years old
#26Amateurs, Firefox has 20+ year old bugs open and just recently fixed an 18 year old one.
I have entirely given up on getting Firefox bugs fixed; considering stuff like the entire browser crashing because the GC gets starved during heavy load [1] to seemingly having no control of their file handles at all [2]... The chromium team is a fair bit more receptive/reactive. I wish Firefox could get their priorities straight. [1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1790500 [2]: https://bugzilla.mozilla…
My experience has tended to be the other way round. I’ve filed quite a few bugs in Firefox over the years, and a handful in Chromium. Filtering to similar sorts of reports (since many of my Firefox reports are using-the-browser related, and often dealing with regressions since I’ve used Nightly for ~11 of the last 13 years, whereas my Chromium reports have only ever been for things like rendering errors), most of my Firefox reports have been dealt with fairly promptly (though some linger), whereas in Chromium I don’t think I’ve ever had prompt action after initial triage—a couple have been fixed incidentally two or more years later due to replacement of a large component, but I think that’s it.
(My experience is almost all more than two years old. Haven’t needed to file much in the last couple of years.)
Re: SVG Chromium bug is more than 10 years old
#27And yet somehow, we all survived. This suggests the right course of action is to explicitly deprecate that use case and throw an error, to decrease the complexity of implementation.
Re: SVG Chromium bug is more than 10 years old
#28Chromium still doesn't support SVG icons in browser extensions either. Not as extension's own icon or in the browser toolbar. Firefox has supported those for years. Chromium just scales the images to the nearest 16-dip.
Re: SVG Chromium bug is more than 10 years old
#29Writing negative replies on bugs like this isn't constructive (like #c89). Browser engineers have an extremely difficult job. The codebase is incredibly complex (they aren't just copying data from one system to another - it takes years to get up to speed in just a small area of the codebase) - any change (even improvements/fixes) risks breaking websites. You might think you are complaining to a faceless organization,…
I admittedly can be sharp in bug reports for obvious breaking bugs with companies like Adobe and Microsoft. I know what it's like from the other end— I worked as a developer for a decade, and before that, I worked in code-level support in a very large dev organization for a few years. Frankly, a lot of the shit I shoveled in support was totally justified, and sadly, the squeaky wheel does often get the grease. Often you don't even make it past support unless you become an "irate customer."
That said, it's pretty clear when you're up against an org like that, and communicating that you are angry because you are experiencing hardship from an unresolved issue in software that you license never, ever warrants personal attacks; implications that the developers are lazy, stupid, or disorganized; implications that they're maliciously withholding fixes, etc etc etc.
And beyond that, there's no excuse for being cranky in bug reports for free software or in small fora like issue reports on repos that go directly to developers, or anything like that.
Re: SVG Chromium bug is more than 10 years old
#30Amateurs, Firefox has 20+ year old bugs open and just recently fixed an 18 year old one.
I have entirely given up on getting Firefox bugs fixed; considering stuff like the entire browser crashing because the GC gets starved during heavy load [1] to seemingly having no control of their file handles at all [2]... The chromium team is a fair bit more receptive/reactive. I wish Firefox could get their priorities straight. [1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1790500 [2]: https://bugzilla.mozilla…
"I wish Firefox could get their priorities straight."
I guess the target for complaining would be rather Mozilla, who rather drastically cut down their engineers. I think those who remain, do all they can, with their limited manpower.