8 ms·
An enhancement request I submitted to Bugzilla 15 years ago was just closed
- bryanrasmussen 5y agoI just found it amusing, I had forgotten all about this it was so long ago. I hope it doesn't turn into a pile-on on mozilla, who after all make my favorite browser.
- ZeroGravitas 5y agoI think if the title had been "A feature I requested 15 years ago got added 5 years ago and someone just noticed my similar issue and closed it", it would have inspired a very different conversation, and is probably a good example of why HN is such a stickler about titles.
- deleted 5y ago[deleted]
- deleted 5y ago[deleted]
- maxbaines 5y agoI found this amusing too. If anything great to see mozilla keep issues active for so long.
- bryanrasmussen 5y agopart of this may be what a great bug tracking tool bugzilla is.
- mrjin 5y agoHuh?
- bryanrasmussen 5y agoimagine keeping a ticket going 15 years in Jira and being able to actually do anything on it.
- shp0ngle 5y agoNo activity for 15 minutes. Stalebot closed this issue.
- willbudd 5y agoUpvote 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 rug.
- wartijn_ 5y ago> 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
- willbudd 5y agoActually, upvoting my comments will beset you on a path to enlightenment and world peace. Source: trust me bro.
- smhg 5y agoCan I suggest to please write what the bug was about in the title as it happens often that old bugs are closed years later.
- bryanrasmussen 5y agoBasically it wasn't a bug but a request to add some capability like security to extensions - useful for more powerful extensions like GreaseMonkey or in this case the one I was using Chickenfoot https://www.sitepoint.com/rewrite-web-chickenfoot/ https://www.sitepoint.com/rewrite-web-chickenfoot/ which allowed you to do all sorts of things in scripts running inside an extension in the browser which might end up being dangerous. Basically extensions have changed a lot in those 15 years so not really surprising it was closed, just amusing that hey, that thing is still around I'd forgotten all about it!
- mariusor 5y agoI think the submission rules specifically frown upon editorializing titles. On the other hand the verbatim title would probably be meaningless to the HN crowd, which leads me to believe that your submission has no real discussion value.
- busymom0 5y agoFew months ago: > Firefox Mac feature implemented 21 years after report > Top reply to the bug report is from Mike Pinkerton and reads: "i can't argue, but it's a time thing." https://old.reddit.com/r/apple/comments/msl1ra/firefox_mac_feature_implemented_21_years_after/ https://old.reddit.com/r/apple/comments/msl1ra/firefox_mac_f...
- Austin_Conlon 5y agoApple responded to a 9 year old bug report saying “much has changed since this was filed” https://twitter.com/siracusa/status/1356681590915682305?s=21 https://twitter.com/siracusa/status/1356681590915682305?s=21.
- sverhagen 5y agoI have to admit that this is pretty much how I regularly close bugs (company-internal). In my case, I admit that there's a level of intentional sloppiness involved. The decision involves a combination of wanting to reduce my backlog to what's relevant, knowing about circumstances and how they have changed, particularly knowing that the area in question has been highly refactored, such that even if the bug technically still existed, its manifestation would be quite different, and the fact that it's been around so long without having bubbled up to the top earlier. Rarely does all hell break loose just because I have removed a bug from our collective memory by closing it prematurely. Also, often I follow the "much has changed" comment by something like: "feel free to reopen if I got it wrong", and people subscribed to the ticket could then respond (which they rarely do).
- deleted 5y ago[deleted]
- boomboomsubban 5y agoClosed because it became irrelevant in Nov 2017. I guess that's resolved.
- scim-knox-twox 5y agoClosed today because it "became irrelevant in Nov 2017"?
- boomboomsubban 5y agoThe "today" was in the title, didn't think I needed to repeat it.
- scim-knox-twox 5y agoYou don't understand, read again
- boomboomsubban 5y agoMy guess is you're pointing out the four year gap between problem "resolved" and closed but that was what I was doing.
- marcosdumay 5y agoClosing is a manual action, and if the bug is not relevant, people won't go there often.
- deleted 5y ago[deleted]
- seumars 5y agoI knew this was about Firefox without looking at the url.
- deleted 5y ago[deleted]
- deleted 5y ago[deleted]
- WalterBright 5y agoWe 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.
- kragen 5y agoIn this case they closed the bug because a competing browser launched with the "bug fix" as one of its most touted features, and Mozilla spent several years rearchitecting Firefox in order to support the requested feature. This is a triumph.
- ibotty 5y agoThat's not how I would describe it and not how it was described at that time. It was deemed necessary to discontinue legacy extensions to improve the browser.
- kragen 5y agoWell, I could be wrong, but as I understand it, the particular way in which the browser was improved is that, now, browser and extension components can be sandboxed, which is what the bug was asking for?
- sam_goody 5y ago> We don't close bugs just because they are old. I SO much appreciate that simple offhand comment. Not, it's been three days, lets use a bot to remove the bug or close what might be a very useful thread for others that get hit by it (and that can comment of a bug is still extant). Though I could see the point in a "dormant" tag, or something that let's other users know that the dev is probably not thinking about the bug now. And I appreciate that Mozilla is still going through them on occasion to see what is still relevant.
- deleted 5y ago[deleted]
- mdoms 5y agoThat's downright rapid by Mozilla standards.
- throw3838 5y agoSome active bugs on my github repo are 9 years old. Pretty common with long lived OS projects.
- alrs 5y agoI've had years-old patches land, if it's any consolation.
- octoberfranklin 5y agoYeah and it was closed by deleting the relevant functionality.
- lioeters 5y agoUnrelated, but seeing Bugzilla reminded me, I was recently delighted to learn that there's been (slow but) steady progress on a 9-year-old ticket. Implement the WebMIDI API - https://bugzilla.mozilla.org/show_bug.cgi?id=836897 https://bugzilla.mozilla.org/show_bug.cgi?id=836897
- 8bitsrule 5y agoWow. I actually lived long enuf to see it! This is super good news. Test pages here: [https://versioduo.com/webmidi-test/ https://versioduo.com/webmidi-test/] and for FF97: [https://github.com/versioduo/webmidi-test https://github.com/versioduo/webmidi-test] ...
- bkmn 5y agoI opened bug #337051 in 2006 and it got closed in 2016. While I can't take any credit for the actual squashing of the bug it feels good having contributed to an important and very long-term project like Firefox.
- deleted 5y ago[deleted]
- LukaszWiktor 5y agoIt was not a bug. It was a feature request.
- tux2bsd 5y agoCan't believe others haven't noticed.
- mritzmann 5y agoI would appreciate it if an HN moderator would change the title.
- saurik 5y agoI 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.)
- pvg 5y agoWithout the made-up title the point is lost but there really isn't much point left, in this case. Bug tracker post titles are an edge case the title rules don't deal with all that well, as you've recently commented yourself. But it's not a particularly important edge case by the expedient that most bug tracker posts (especially to live bugtrackers) are lousy HN posts to begin with.
- zinekeller 5y agoWhile I agree, before issues were called issues they were called bugtickets (regardless if it's actual defects waiting to be fixed or feature requests).
- juloo 5y ago
- ZeroGravitas 5y agoIs a RFE technically a bug?
- hnplj 5y ago
- mrjin 5y agoThought M$ was the worst. In VisualStudio 2008 they introduced a really annoying bug that in environments that had non-English IMEs installed, when there was a compilation error, the default IME would be invoked, and of course, when you tried to fix the error, what you typed would make nonsense to the compiler. Contacted M$, they promised thatit would be fixed in VS2008 SP1. But the fact was they never made it until some versions of VS2016. When it was fixed, those IMEs had been removed from my dev envs for ages.
- deleted 5y ago[deleted]
- tonyedgecombe 5y agoLogging issues with a big company like Microsoft or Adobe feels like talking to a brick wall. I don't bother wasting my time on it anymore.
- mrjin 5y agoNeither do I. Was too naive...
- dools 5y agoHey this happened to me last year! A bug I opened for PHP in 2006 got fixed in 2021, 15 years too :) https://bugs.php.net/bug.php?id=39579&edit=2 https://bugs.php.net/bug.php?id=39579&edit=2
- deleted 5y ago[deleted]
- kenrick95 5y agoFew months ago QA at my workplace found a bug with my work but I couldn't reproduce it. Turns out they're using Chrome and I'm using Firefox, and after reading some docs & specs, I concluded that Firefox's behavior is not correct. I'm about to file a bug and turns out that I found a same issue that's filed 20 years ago, and it's still open today: https://bugzilla.mozilla.org/show_bug.cgi?id=156090 https://bugzilla.mozilla.org/show_bug.cgi?id=156090 Quite amusing...
- deleted 5y ago[deleted]
- TBurette 5y agoI 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 freely without impacting extensions and it is possible to implement features such as sandboxing.
- stkdump 5y agoYes. 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 that it is hard to compete with google.
- throwawaylinux 5y ago> Yes. It's a shame that the firefox user base is so easy to outrage. Firefox's user base was a third of all internet users a little over 10 years ago. Now it's as little as 5%. The "the users are wrong" attitude might not have been the main cause of the decline but it has been a real factor, IMO. > 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 that it is hard to compete with google. In Firefox's heyday when they were a scrappy underdog they took on King Kong on its home turf (the Windows desktop) and won (or at least took a huge chunk of market share). The idea that what has now become a big rich company that makes nearly half a billion dollars a year from their browser somehow doesn't have the resources to make that browser competitive is hard to believe.
- 5y ago
- mdtrooper 5y agoWell, 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 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." Miguel "I know what the standard says, that's why I set this bug to WONTFIX rather than INVALID" Robert Longson [:longsonr]
- deleted 5y ago[deleted]
- kbelder 5y agoThere needs to be a SHOULDBUTWONT status.
- pjc50 5y agoI have a comment on a feature request that's 22 years old and still open: https://bugzilla.mozilla.org/show_bug.cgi?id=57342 https://bugzilla.mozilla.org/show_bug.cgi?id=57342 Less relevant now, as fewer sites show files inline.
- bocytron 5y agoA commenter said "Yes, WONTFIX and INVALID seem a bit much. We'll just keep it in the database for eons." I wonder how they knew how right they were.
- whodev 5y agoThis reminds me of a GCP issue that was opened in 2011 for users not being able to remove themselves from projects. It affects me still, I got an invite from a friend for a little hobby project he was working and he lost access to his Google and now I can't remove it from my GCP. https://issuetracker.google.com/issues/35889152?pli=1 https://issuetracker.google.com/issues/35889152?pli=1
- jpswade 5y agoThis bug is from 20 years ago and still isn't solved. https://bugzilla.mozilla.org/show_bug.cgi?id=122752 https://bugzilla.mozilla.org/show_bug.cgi?id=122752 Incredible really how things have moved on since this issue.
- deleted 5y ago[deleted]
- wickedpickle 5y agoBetter late than never I guess?
- codesuki 5y agoAbout 4 years ago I filed a bug report about tabs opened from a pinned tab not opening as the rightmost tab (it opens as the first tab). I also tried to write a patch for it, but the issue is still open. Anyway, how is Mozilla to work for? I always thought it must be great, but recently reading about the firings and project cancellations it doesn't seem so rosy anymore.
- hnarn 5y agoI don't find this that interesting since the bug was not "fixed" in the sense most people probably think about fixing a bug -- i.e. someone picks it up, investigates it and writes a fix. It was closed due to housekeeping since, as the latest comment states: > "legacy" extensions are gone While I agree that housekeeping large backlogs is commendable, this bug was if anything fixed by "accident", and is no more a fix in the traditional sense than closing a bug for an EOL operating system because the issue described no longer exists.
- dotancohen 5y agoNot really. The real feature being asked for was to prevent arbitrary extensions from accessing the filesystem. That specific request has been granted, as WebExtensions cannot access the filesystem. The situation that no other "safe" method of accessing the filesystem was not even considered by the bug's author, but it does address the issue.
- WhyNotHugo 5y ago> WebExtensions have various permissions associated (though not controllable by the user -- merely declared and accepted or not I think this is a major flaw in how permissions are implemented in Firefox (and Flatpak and other pieces of modern technology). Software commonly "declares" what permissions it wants, but the user doesn't have to opt-in to grant these permission. They're granted by default, and there's usually no way to deny it. I think iOS has a good approach here, where an application asks for camera permission and there's two buttons: Grant or Deny. The prompt also comes when camera access is actually required, not at software installation time.
- stevage 5y agoExactly the same as Android then?
- benibela 5y agoThat reminds me that last month I got a notification on a bug I opened 14 years ago on the Lazarus project (a cross-platform GUI project) But my bug was not closed, they just asked if it is still a relevant issue...
- matt_kantor 5y agoThis bug I had open against Chrome for almost 12 years (note the re-filing) was closed as WontFix recently: https://bugs.chromium.org/p/chromium/issues/detail?id=142241 https://bugs.chromium.org/p/chromium/issues/detail?id=142241
- einpoklum 5y agoIn the bug page, we see the initial response: > That's a good idea. We can look into it, but I suspect that doing it right will require either crippling Chickenfoot substantially, or doing substantial rewiring of Firefox itself. The direction Firefox decided to go was mostly "crippling substantially" of extensions, and not enough "rewiring of Firefox itself".
- motorpsycho 5y agoAnother 'enhancement' issue from 1999, resolved in 2018 with 'wontfix'. https://bugzilla.mozilla.org/show_bug.cgi?id=14328 https://bugzilla.mozilla.org/show_bug.cgi?id=14328 It was about SRV records (RFC 2052, RFC 2782) that could have been used with HTTP(S) too, but no browser supported it. 2019 the IETF released the first draft for HTTPS records https://datatracker.ietf.org/doc/draft-ietf-dnsop-svcb-https/ https://datatracker.ietf.org/doc/draft-ietf-dnsop-svcb-https... 2021 Firefox 92 supports HTTPS records https://www.mozilla.org/en-US/firefox/92.0/releasenotes/ https://www.mozilla.org/en-US/firefox/92.0/releasenotes/ Only 22 years.