SVG Chromium bug is more than 10 years old
bugs.chromium.org
SVG Chromium bug is more than 10 years old
1–10 of 60 posts
Re: SVG Chromium bug is more than 10 years old
#2The `` 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.
One commenter puts it into perspective:
"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."
Re: SVG Chromium bug is more than 10 years old
#3Seems like the guy from Opera has implemented the first 90% of it. Now only the remaining 90% left.
Re: SVG Chromium bug is more than 10 years old
#4The ` ` 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. One commenter puts it into perspective: "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…
I mean that commenter also didn't fix it in the last ten years. Chromium is open source isn't it?
Maybe the commenter is less than ten years old. Otherwise they have as little excuse as the rest of us.
Re: SVG Chromium bug is more than 10 years old
#5The ` ` 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. One commenter puts it into perspective: "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…
I mean that commenter also didn't fix it in the last ten years. Chromium is open source isn't it? Maybe the commenter is less than ten years old. Otherwise they have as little excuse as the rest of us.
This is such a bad faith argument whenever I see it, when an end-user is commenting on a project, at least that is funded and has a dedicated team working on it. Asking for something to be fixed, doesn't have to warrant such a reply.
I can see if it was some obscure project or some solo dev project, but it's run by Google for gods sake.
People don't like it, but even if you are a solo dev open sourcing your stuff a product that expects non tech people/even Js developers, expecting them to open a PR for your coded in some low level language instead of letting you know how much priority it might take is wrong IMHO.
Re: SVG Chromium bug is more than 10 years old
#6The ` ` 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. One commenter puts it into perspective: "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…
I get the frustration but on the other hand there’s an expectation here that the software must be absolutely bug free and I just don’t see that ever happening.
To look at the metric another way: 10 years, 120 months. 95 comments (including all kinds of automated comments). So less than one a month, among a small group of people. Fixing the bug is clearly not just a one-line thing and requires a ton of effort (including the loading of external resources, which always requires security consideration), which doesn't bode well when compared with the size of audience clamouring for it.
The reality is that it just isn’t that important.
Re: SVG Chromium bug is more than 10 years old
#7Earlier quoted context omitted.
I mean that commenter also didn't fix it in the last ten years. Chromium is open source isn't it? Maybe the commenter is less than ten years old. Otherwise they have as little excuse as the rest of us.
This is such a bad faith argument whenever I see it, when an end-user is commenting on a project, at least that is funded and has a dedicated team working on it. Asking for something to be fixed, doesn't have to warrant such a reply. I can see if it was some obscure project or some solo dev project, but it's run by Google for gods sake. People don't like it, but even if you are a solo dev open sourcing your stuff a p…
What we also forget is that Chromium (+ HTML, Javascript, SVG, ect) is starting to be in a market dominance position where Windows was in past decades: We're at the mercy of a market winner who improves it at their pace.
At times, it appears that web standards have evolved from their open nature to primarily supporting Google's agenda. If Google wants a certain product to run the browser, they will bend the standards to do that.
I bet as soon as a Google product needs this feature, the bug will be fixed.
Re: SVG Chromium bug is more than 10 years old
#8The ` ` 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. One commenter puts it into perspective: "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…
I mean that commenter also didn't fix it in the last ten years. Chromium is open source isn't it? Maybe the commenter is less than ten years old. Otherwise they have as little excuse as the rest of us.
> Chromium is open source isn't it?
Being open source doesn't mean that you can contribute to it at all. In this particular case, Google does actually take contributions, but only from people who signed their CLA, and many people aren't going to agree to that.
Re: SVG Chromium bug is more than 10 years old
#9Earlier quoted context omitted.
I mean that commenter also didn't fix it in the last ten years. Chromium is open source isn't it? Maybe the commenter is less than ten years old. Otherwise they have as little excuse as the rest of us.
This is such a bad faith argument whenever I see it, when an end-user is commenting on a project, at least that is funded and has a dedicated team working on it. Asking for something to be fixed, doesn't have to warrant such a reply. I can see if it was some obscure project or some solo dev project, but it's run by Google for gods sake. People don't like it, but even if you are a solo dev open sourcing your stuff a p…
I agree with what you are saying.
But this guy from Russia came in, threw a fit and was never heard again in this bug.
And still, the reply was polite.
I am sure there are tons of more bugs in the chromium project that are 10 years or older. Some things are just more critical than other.
Re: SVG Chromium bug is more than 10 years old
#10Amateurs, Firefox has 20+ year old bugs open and just recently fixed an 18 year old one.