Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

SVG Chromium bug is more than 10 years old

bugs.chromium.org

Post reply on HN
Print view View original

31–40 of 60 posts

Re: SVG Chromium bug is more than 10 years old

#31

Post by shadowgovt »

gwbas1c wrote: post #7
anaganisk wrote: post #5

Earlier quoted context omitted.

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…

Oh, probably. That's a pretty standard pattern; I know of a feature that was lacking from Apple's window manager until they found a need for QuickTime to use it and added it in.

Re: SVG Chromium bug is more than 10 years old

#32

Post by jansan »

chrismorgan wrote: post #26
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…

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…

I once had a fantastic experience with reporting a bug on Firefox. One engineer saw that the bug was severe enough to justify delaying the release process, they worked their asses off to fix the bug and merged the bug into the new version which was released with just a little delay. That was amazing to watch.

In general I have the feeling that Firefox and Chromium developers take bug reports very seriously. Safari is a different story, my bug reports there got frequently ignored. But I have the feeling that the entire Safari project is handled by one single developer, so it's not really surprising.

Re: SVG Chromium bug is more than 10 years old

#34

Post by shadowgovt »

tansan wrote: post #21
nashashmi wrote: post #12

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.

The implementation needed is very non-trivial and the problem crops up too infrequently to justify shifting priorities to fix it.

Re: SVG Chromium bug is more than 10 years old

#35

Post by shadowgovt »

rnantes wrote: post #22

https://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.

Apple should probably get on fixing that; their new architecture broke a popular application on their platform, and that could cost them users.

(I'm being tongue-in-check, but those who know the story of Microsoft beating up their APIs to keep Adobe happy know that's actually how this goes sometimes. "Who's gonna pay the cost for this being broken?" is a business concern as much as a technical one).

Re: SVG Chromium bug is more than 10 years old

#36

Post by duped »

bagacrap wrote: post #4
tansan wrote: post #2

The ` ` 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.

Have you ever looked at the Chromium source code?

Re: SVG Chromium bug is more than 10 years old

#37

Post by bsimpson »

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

bfgeek has been a TL on Blink for many years. Dude is speaking from his expertise.

Re: SVG Chromium bug is more than 10 years old

#38

Post by sebazzz »

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.

Well, some bugs actively hurt their ecosystem, like the bug in Firefox for iOS that sends corrupt or missing cookies after the application has been tombstoned and is launched again[0]. This will cause you to get logged out of many sites, which in turn makes you use a different browser and at that point you might as well use Chromium on your desktop as well.

[0] https://github.com/mozilla-mobile/firefox-ios/issues/12279

Re: SVG Chromium bug is more than 10 years old

#39

Post by charcircuit »

masukomi wrote: post #16
vbezhenar wrote: post #14

Earlier quoted context omitted.

What would happen if you throw a patch into their discussion without signing CLA and with WTFPL license? Can someone else take that patch and resubmit it with proper procedure? Sounds like a good approach if you want bug fixed but don't want to sign any agreements.

WTFPL is not a good license for the same reason that "public domain" isn't good. It's not actually recognized internationally. Copyright is the basis of viable international licenses and they need you to turn over the copyright to them (or license it to them or whatever their CLA says). So, if you did that it'd probably be worse than useless because it might hamper the legal adoption of identical or near-identical co…

https://opensource.google/documentation/reference/thirdparty...

Google allows WTFPL third party code.

Re: SVG Chromium bug is more than 10 years old

#40

Post by tripflag »

chrismorgan wrote: post #26
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…

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…

I feel that Firefox has been increasingly focusing on adding fancy new features rather than ensuring the browser is stable and functional. Accounts, Sync, Pocket, to name some examples.

If we include the android edition it's easy to mention the UX customization options as another example. "Scroll to hide toolbar" frequently breaks the viewport size calculation, making it impossible to scroll to the bottom of most pages. "Pull to refresh" keeps triggering when trying to scroll up on pages. "Swipe toolbar to switch tabs" is great, even though it occasionally sends you to the new-tab splashpage which I'm still not quite sure how to effectively return from. And the decision to make most addons unavailable is just confusing through and through.

I get the motivation to add "some value" to set Firefox apart from the competition; I just wish it was a far second to bugfixes.

Post reply on HN