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

An enhancement request I submitted to Bugzilla 15 years ago was just closed

bugzilla.mozilla.org

Post reply on HN
Print view View original

81–90 of 129 posts

Re: An enhancement request I submitted to Bugzilla 15 years ago was just closed

#81

Post by saurik »

mritzmann wrote: post #43
LukaszWiktor wrote: post #23

It was not a bug. It was a feature request.

I would appreciate it if an HN moderator would change the title.

I agree that that should be changed, but dollars to donuts (as I have seen this happen many times before) the moderators rename it to the title of the bug and the entire point is lost ;P. (Though maybe they read this and think again; in the future to make such a point you first need to write a comprehensive article on your own blog with this as the title and then you mostly get to editorialize all you want... you just need to make sure it has enough heft to it to avoid anyone considering it "blog spam" and thereby changing the link in addition to the title ;P.)

Re: An enhancement request I submitted to Bugzilla 15 years ago was just closed

#82

Post by fartcannon »

stkdump wrote: post #55
TBurette wrote: post #53

I remember that the introduction of the new WebExtension API to replace the existing extension system was heavily criticized. The old system gave extensions deep access to the browser and the new extension API (copied over from the Chrome browser) was seen as a limiting dumbing down. It was a painful transition but very much needed. Now extensions don't clash with one another. The browser code can be modified more fr…

Yes. It's a shame that the firefox user base is so easy to outrage. Same with the more recent change ragrding tabs. I am using firefox for a very long time now, and I just don't see that firefox is massively going downhill so far, like many people seem to suggest. Of course I am bummed out that certain features could not be retained (such as installable PWAs on desktop). But these are just the realities of the fact t…

If youre not outraged, or at least don't understand why they're outraged, you must not understand what's happening.

Re: An enhancement request I submitted to Bugzilla 15 years ago was just closed

#83

Post by willbudd »

wartijn_ wrote: post #80
willbudd wrote: post #70

Earlier quoted context omitted.

Upvote me if you absolutely detest stalebot. Closing issues after a while if the reporting user fails to follow up on a request for additional information can be useful. But more often than not these stalebots kick in because the maintainer(s) never chimed in. Don't use a bot that can't distinguish between those two cases unless your only aim is to wage war on your users and sweep everything inconvenient under the ru…

> Upvote me if you absolutely detest stalebot. What good would that do? Seems to me that up or downvoting a HN comment won't have any effect on TN usage of Stalebot

Actually, upvoting my comments will beset you on a path to enlightenment and world peace. Source: trust me bro.

Re: An enhancement request I submitted to Bugzilla 15 years ago was just closed

#84

Post by [deleted] »

TBurette wrote: post #53

I remember that the introduction of the new WebExtension API to replace the existing extension system was heavily criticized. The old system gave extensions deep access to the browser and the new extension API (copied over from the Chrome browser) was seen as a limiting dumbing down. It was a painful transition but very much needed. Now extensions don't clash with one another. The browser code can be modified more fr…

[deleted]

Re: An enhancement request I submitted to Bugzilla 15 years ago was just closed

#85

Post by adrianN »

ZeroGravitas wrote: post #64
BoppreH wrote: post #56

Earlier quoted context omitted.

My two most important extensions were my adblocker, and Vimium (enable Vim-like control in Firefox). The new WebExtension API broke Vimium, with no replacement possible[1]. Meanwhile, I never had problems with extension clashes. I appreciate that this improved the code base quality for Mozilla folks, but it was a significant step down in features for me. I even switched to Vivaldi (which has built-in Vim keybindings)…

There are workarounds for many of these things, to differing degrees. The genius of open source is that you can even fork the browser if your target audience is geeky enough, while not exposing your friends and family to malware in their standard browser.

Forking something as complex as a browser is doomed to fail unless you have a lot of money. Sooner rather than later you won't be able to port patches and shortly after your fork will be riddled with security issues and incompatibilities.

Re: An enhancement request I submitted to Bugzilla 15 years ago was just closed

#86

Post by [deleted] »

[deleted] wrote: post #84
TBurette wrote: post #53

I remember that the introduction of the new WebExtension API to replace the existing extension system was heavily criticized. The old system gave extensions deep access to the browser and the new extension API (copied over from the Chrome browser) was seen as a limiting dumbing down. It was a painful transition but very much needed. Now extensions don't clash with one another. The browser code can be modified more fr…

[deleted]

[deleted]

Re: An enhancement request I submitted to Bugzilla 15 years ago was just closed

#87

Post by [deleted] »

mdtrooper wrote: post #58

Well, I have a bug open (now it is wrong closed) in 2016 about firefox in their bugtracker: "The onload event is not fired with the symbols are loaded in a svg" https://bugzilla.mozilla.org/show_bug.cgi?id=1254159 The last messages were: "Well, the standard documentation (w3c) says there is "onload" event, then Firefox does not comply the SVG standard...because the performance is important....it is sounds good." Migu…

[deleted]

Re: An enhancement request I submitted to Bugzilla 15 years ago was just closed

#88

Post by adrianN »

krageon wrote: post #66
juloo wrote: post #60

Earlier quoted context omitted.

I've been using Vimium since I use firefox (for around 3 years). It's annoying that Vimium can no longer control the browser UI and is limited on some pages (New Tab, mozilla.org) but this is necessary for security.

> this is necessary for security Why? You can't read the source of this addon and evaluate whether or not it should have this access? This should be a permission that you can grant to an addon, we're not children that must at every juncture be managed so they don't burn their fingers.

No, almost nobody can read the source code of every addon. Even the people who can won't be able to spot malicious behavior unless it's very obvious.

Re: An enhancement request I submitted to Bugzilla 15 years ago was just closed

#90

Post by sokoloff »

Dave3of5 wrote: post #30
WalterBright wrote: post #12

We don't close bugs just because they are old. Priority on fixing bugs is some combination of their severity, the number of users affected, and the difficulty/disruption involved in fixing it. The age is not relevant.

Surely age is relevant though. If something is very old it's priority should increase as it's in danger of never being fixed in the lifetime of the product or being superseded when the feature is re-architected / removed.

Is the point of priority to fix that issue or to improve the product? If it’s the former, old bugs should increase in priority.

If globally improving the product is the goal, deprioritizing (or leaving alone) old issues is probably more reasonable. “We’ve lived with it for this long; how critical could it really be?” In this case, the risk of never being fixed is a feature, not a bug.

See also Lindy Effect https://en.m.wikipedia.org/wiki/Lindy_effect

Post reply on HN