Writing negative replies on bugs like this isn't constructive (like #c89).<p>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.<p>You might think you are complaining to a faceless organization, but in reality your really just talking to 1-2 people. Be kind. Each time an engineers gets dumped on you risk them throwing in the towel for good (engineer burnout is real), your bug will very much not be fixed then.<p>Engineers like fs@ are one of a kind and experts in their area. (fs@ implemented SVG favicons to Chromium for example - <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=294179" rel="nofollow noreferrer">https://bugs.chromium.org/p/chromium/issues/detail?id=294179</a> ). As the web platform is so expansive there are really only a few people in the world at one time who understand various problems deeply enough to make progress on a fix.<p>What does help? In this particular case - if you are affected by this bug starring it helps. If you can kindly describe how this affects you - that also helps. The Chromium project actively tracks highly starred bugs. (Keep in mind the project also takes into account "gaming" the count so getting 100 people to star the bug mindlessly wont help).
The `<use>` element in SVG can target an external source and clone it into the shadow DOM. However, there is a bug that prevents it from copying certain elements resulting in an unexpected SVG.<p>One commenter puts it into perspective:<p>"How is this still not fixed 10 years later? This bug is now just as old as Voyager 1 leaving the solar system or Lana Del Rey debut album. We went through an entire Spider Man reboot cycle and 3 James Bond movies. A whole generation of consoles came and passed by with PlayStation 4 being both released and superseded by PlayStation 5 while this bug was open. This bug is older than Grand Theft Auto 5. We live in a whole different world now, especially considering the pace web is developing and we STILL cannot store an icon with a gradient in an external SVG sheet."
And???<p>Sometimes a bug just doesn't have the same importance to the maintainers as it does to you.<p>If it's <i>that</i> important, fix it yourself.
let's go through this again: just because a specific bug might be important to _you_ does not mean it is important to anyone else. You might thing bug 109212 is obviously important, but there are hundreds, if not thousands of other bugs that are just as old, that might be important to someone else. The Chrome folk fix the bugs either directly important to them/google, and the bugs that are important to the most people. That's basic prioritization, and anyone who thinks that bug priority should be a function of age, rather than real world impact is bad at prioritizing.<p>This also isn't a solvable problem: Google cannot simply hire more people to fix more bugs (mythical man month, remember?).<p>The reality is that if you have a pet bug, that is specifically important to you, and not important to anyone, is not a security bug, and isn't a feature regular users or web devs are clamoring for, you're probably going to need to fix it yourself (or pay someone else to). Given a choice between paying an engineer to spend time fixing a bug that has no significant impact, and paying that same engineer to work on something that thousands/millions will benefit from, or something google directly benefits from, google (or any employer) is going to choose one of the latter options. That's just sensible management.
<a href="https://bugs.chromium.org/p/chromium/issues/detail?id=1305733" rel="nofollow noreferrer">https://bugs.chromium.org/p/chromium/issues/detail?id=130573...</a><p>Vector GPU Rasterization in Chrome is still broken on Apple Silicon Macs. Has been for more than a year.
And 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.
Chromium 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.
These complaints about Chromium and Firefox bugs make me sad. Wasn’t the whole point of open source putting the user in control. That way they did not have to go begging to the vendor to pretty please fix this bug that is affecting them.<p>What is the difference between these begging, cajoling bug reports and similar bug reports for proprietary closed source software?<p>Seems the software is just as centralized and the commercial company is just as much in charge versus the user.
<a href="https://stackoverflow.com/questions/33087256/how-to-gradient-fill-an-svg-from-an-external-stylesheet" rel="nofollow noreferrer">https://stackoverflow.com/questions/33087256/how-to-gradient...</a><p>A developer running in to problems trying to use this