SVG Chromium bug is more than 10 years old • Hacker News Board

Re: SVG Chromium bug is more than 10 years old

#51

Post by coldtea » Mon, Jul 24, 2023, 8:26 PM UTC

anaganisk wrote: post #5

bagacrap wrote: post #4

Earlier 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…

>but it's run by Google for gods sake

So? Google still has a team assigned to the project, and that team has limited people, and it also has preferences and priorities.

Re: SVG Chromium bug is more than 10 years old

#52

Post by IshKebab » Mon, Jul 24, 2023, 8:59 PM UTC

jlarocco wrote: post #24

And??? 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.

Yeah... There are 10 year old Android bugs that annoy me too and "fix it yourself" is a terrible answer.

You know exactly what would happen. You make PR, and then.... Nothing. Enjoy all that wasted effort.

Re: SVG Chromium bug is more than 10 years old

#53

Post by alexanderpas » Mon, Jul 24, 2023, 10:37 PM UTC

bfgeek wrote: post #20

Writing 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,…

To be fair, #c89 was posted in Q4 2021, almost 2 years after the last post from the devs in Q1 2020 which said the bug would be fixed in Q1, and there was no response on an earlier request for a status update.

Re: SVG Chromium bug is more than 10 years old

#54

Post by jlarocco » Tue, Jul 25, 2023, 3:00 AM UTC

IshKebab wrote: post #52

jlarocco wrote: post #24

And??? 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.

Yeah... There are 10 year old Android bugs that annoy me too and "fix it yourself" is a terrible answer. You know exactly what would happen. You make PR, and then.... Nothing. Enjoy all that wasted effort.

First of all, I don't know that would happen - it looks like the maintainers are open to the patches.

And second, it's still not wasted effort if you get the fix that you need.

Re: SVG Chromium bug is more than 10 years old

#55

Post by tansan » Tue, Jul 25, 2023, 3:11 AM UTC

shadowgovt wrote: post #27

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.

Browsers can't really unilaterally deprecate W3C standards especially when its already implemented in competing browsers.

Re: SVG Chromium bug is more than 10 years old

#56

Post by tansan » Tue, Jul 25, 2023, 3:13 AM UTC

jlarocco wrote: post #24

And??? 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.

I thought it was cool to find an issue this old and still being worked on, so I shared it. It was nice seeing how much work goes into it.

What's your problem?

Re: SVG Chromium bug is more than 10 years old

#57

Post by bagacrap » Tue, Jul 25, 2023, 4:53 AM UTC

varjolintu wrote: post #49

bagacrap wrote: post #47

Earlier quoted context omitted.

What do you think is going to happen before it's displayed?

Magic of course. Talking seriously, it's one more step you'll have to take care of when making extensions for multiple browsers. Using SVG's directly would be much more simple for the devs.

I thought you were suggesting chromium automatically scaled the SVG for the various sizes it needs. Are you saying you have to do it manually? That does sound like a nuisance.

Re: SVG Chromium bug is more than 10 years old

#58

Post by kasabali » Tue, Jul 25, 2023, 8:56 AM UTC

hutzlibu wrote: post #30

tripflag wrote: post #15

Earlier quoted context omitted.

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.

Mozilla corp.'s misaligned priorities far predates drastically cutting down their engineering force.

Re: SVG Chromium bug is more than 10 years old

#59

Post by IshKebab » Tue, Jul 25, 2023, 6:37 PM UTC

jlarocco wrote: post #54

IshKebab wrote: post #52

Earlier quoted context omitted.

Yeah... There are 10 year old Android bugs that annoy me too and "fix it yourself" is a terrible answer. You know exactly what would happen. You make PR, and then.... Nothing. Enjoy all that wasted effort.

First of all, I don't know that would happen - it looks like the maintainers are open to the patches. And second, it's still not wasted effort if you get the fix that you need.

> And second, it's still not wasted effort if you get the fix that you need.

Putting aside the impracticality of building Chrome or Android from source in perpetuity - and the fact that you'd actually end up with Chromium and AOSP - what good does it do if you fix a bug for one user? You still have to deal with it existing for 99.99999% of users in your app/website.

Re: SVG Chromium bug is more than 10 years old

#60

Post by saurik » Wed, Jul 26, 2023, 3:16 PM UTC

bfgeek wrote: post #20

Writing 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 dunno... that comment you linked to was clearly annoyed and not terribly useful, but I will note that it was at least funny; I got a lot of flack as a single-person maintainer of open source projects and I wouldn't have been much at all phased by that comment (and neither, it seems, was fs@) even though in my case it would have inherently been a lot more personal as I would have no one else to shift the blame to.

Regardless, the answer to that comment says that the reason why this but wasn't fixed yet is due to "priorities"... which I guess makes sense as Google would rather allocate people to working on Web Environment Integrity than bulking up the "1-2 people" you say are working on this part of the code. Remember: the large tech monopoly isn't our friend, and the people who work choose to work at one deserve our collective scorn.