Because browser engineers need to work on more useful features such as EME or Web Environment Integrity API
SVG Chromium bug is more than 10 years old
41–50 of 60 posts
Re: SVG Chromium bug is more than 10 years old
#42Earlier 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…
This is called "the paranoid style", political scientists talk about it as a unique feature of American politics.
It's hard to interact with because falsifying it requires invoking it yourself.
ex. here, we'd have to say "I bet you'd be right here complaining if it was fixed that Google was allowing arbitrary remote loads in not provably secure context." It requires a whole lot of supposition and negativity.
Re: SVG Chromium bug is more than 10 years old
#43These 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.
What is the difference between these begging, cajoling bug reports and similar bug reports for proprietary closed source software?
Seems the software is just as centralized and the commercial company is just as much in charge versus the user.
Re: SVG Chromium bug is more than 10 years old
#44Amateurs, 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…
"no control of file handles at all" seems like an unfair categorization of the actual issue: file handles backing the JavaScript object are closed when the object is GC'ed, which may not happen immediately after it's done being used.
I'm not sure how this could be fixed. Knowing that the file isn't used anywhere else after you upload it would require a full gc pass in the general case even if it's obvious in your snippet, right?
I'm on my phone or I'd check if chrome on Linux has the same issue. Do you know?
Never closing the file handle on macOS is much more serious, but you don't mention that in the body of your bug report, just on your linked page with a repro demo.
Re: SVG Chromium bug is more than 10 years old
#45Earlier 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…
"no control of file handles at all" seems like an unfair categorization of the actual issue: file handles backing the JavaScript object are closed when the object is GC'ed, which may not happen immediately after it's done being used. I'm not sure how this could be fixed. Knowing that the file isn't used anywhere else after you upload it would require a full gc pass in the general case even if it's obvious in your sni…
Chrome behaves correctly on Linux, macos and windows, I can confirm that much. Files are immediately closed when they are no longer in use, either by a FileReader() or by an XmlHttpRequest.
Firefox /appears/ to immediately be closing files as well, as long as they are only accessed by a FileReader and not by an XmlHttpRequest, however this could just be luck.
And I agree my phrasing was suboptimal on that part. I recall that was the first impression I had when encountering the issue and misremembered the details.
Re: SVG Chromium bug is more than 10 years old
#46Earlier 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…
Posting this link to HN (and then describing some unrelated events of the last decade) is asking for it to be fixed? No, it's just griping loudly about one's pet bug, which is one of a zillion in a project as large as Chromium, hoping that somehow this shames Google into reprioritizing it.
Re: SVG Chromium bug is more than 10 years old
#47Chromium 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.
What do you think is going to happen before it's displayed?
Re: SVG Chromium bug is more than 10 years old
#48Earlier 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…
But Chromium is open source. Opera and Microsoft, among others, contribute frequently. Igalia is a consulting firm that takes commissions for Chromium browser work. So the correct statement would be that anyone with enough time and/or money could make this work, not just Google.
Re: SVG Chromium bug is more than 10 years old
#49Chromium 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.
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.
Re: SVG Chromium bug is more than 10 years old
#50let'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.
This also isn't a solvable problem: Google cannot simply hire more people to fix more bugs (mythical man month, remember?).
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.