Firefox bug gets fixed after 25 years

Ha! I was subscribed to this bug for most of those 25 years. Note that Firefox didn&#x27;t exist at the time, this was filed against Netscape Navigator.<p>Don&#x27;t remember why I was subscribed to the bug, must have commented on it or something. Got the occasional email notification about it over the years, always got a chuckle out of it. Then a couple of days ago, lo and behold, it was fixed!

Off topic but I really dislike the trend of using “human readable durations” like “a month ago”, just tell me the bloody date, I can figure out for myself.<p>Outlook (Mac version at least) is the worst offender. For emails prior to the current day it will say for example just “yesterday” and it will only show you the time if you click on the email. I get dozens of mails per day, having just “yesterday” for 50 messages in a row is useless.

Firefox&#x27;s Bugzilla is certainly one of the oldest running bug trackers. I&#x27;m impressed at how much of the original feel of the bug tracker is still around after all these revisions. It was a pretty hairy, monstrous codebase back in the day.<p>At one point in 2000 (?) I stood up an instance in our Windows dev shop to replace a home-grown bugtracker built on Microsoft Access&#x2F;Outlook. It was complex but pretty much one of the best-of-breed bugtrackers for some time. I think that FogBugz was just getting started around then, and those guys were one of the first teams to really consider user experience.

It warms the cockles of my heart to see this kind of thing. Happened to me recently with a 24 year old firefox bug: <a href="https:&#x2F;&#x2F;bugzilla.mozilla.org&#x2F;show_bug.cgi?id=62151" rel="nofollow">https:&#x2F;&#x2F;bugzilla.mozilla.org&#x2F;show_bug.cgi?id=62151</a>

The one long term open bug that irks me the most is that you cannot properly date-format the x-axis of scatter plots in LibreOffice:<p><a href="https:&#x2F;&#x2F;bugs.documentfoundation.org&#x2F;show_bug.cgi?id=54132" rel="nofollow">https:&#x2F;&#x2F;bugs.documentfoundation.org&#x2F;show_bug.cgi?id=54132</a><p>12 years old. According to the comments, fixing it is discouraged as the code is so &quot;horribly complicated&quot;, it would likely cause regressions.

Hoping they do XDG next. Also been waiting for 20 years [1]<p>[1] <a href="https:&#x2F;&#x2F;bugzilla.mozilla.org&#x2F;show_bug.cgi?id=259356" rel="nofollow">https:&#x2F;&#x2F;bugzilla.mozilla.org&#x2F;show_bug.cgi?id=259356</a>

I wish the bug where the copy option is randomly greyed out even though there is text to copy got finally fixed. It&#x27;s been driving me insane.

AWS solves this problem by periodically wiping out old bugs and any mention of them.

Related from last August:<p><i>Happy 25th Birthday to Bugzilla</i><p><a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=37279543">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=37279543</a>

That&#x27;s awesome! 28-03-2000 is not 25 years ago, tho.

BugBot was on to something: <a href="https:&#x2F;&#x2F;bugzilla.mozilla.org&#x2F;show_bug.cgi?id=33654#c190" rel="nofollow">https:&#x2F;&#x2F;bugzilla.mozilla.org&#x2F;show_bug.cgi?id=33654#c190</a><p>&quot;The severity field for this bug is relatively low, S3. However, the bug has 27 duplicates, 103 votes and 91 CCs. :emilio, could you consider increasing the bug severity?<p>For more information, please visit auto_nag documentation.&quot;

On a related note, starting today, I noticed that x.com (fka Twitter.com) is no longer working in Firefox.<p>I get the following error:<p>&gt; Something went wrong, but don’t fret — let’s give it another shot.<p>&gt; Firefox’s Enhanced Tracking Protection (Strict Mode) is known to cause issues on x.com

Textareas are so overlooked, they feel really like 1990s, yet there is no real alternative with spellchecking and os integration.

I&#x27;m still holding hope that thunderbird will actually fetch mail into folders without having to click on them...

At least they don&#x27;t sweep bugs under the rug after 6 months of inactivity as many projects.

Why so many posts about Firefox bugs getting fixed after N years? <a href="https:&#x2F;&#x2F;hn.algolia.com&#x2F;?q=firefox+bug+years" rel="nofollow">https:&#x2F;&#x2F;hn.algolia.com&#x2F;?q=firefox+bug+years</a>

With such old bugs I often wonder whether it&#x27;s not best to simply close them. Few people will browse them and many will be &quot;accidentally&quot; closed by reworking of different subsystems. But if they are still relevant somebody will file it, again. If not reopened it&#x27;s probably not a problem anymore.

&gt; Closed: 24 years ago → 6 hours ago

5 more years than what Phil Leotardo spend in the can, and 7 more than what it took to get a file picker thumbnail in Gnome.

There are a few other long running software. What&#x27;s the longest age of a fixed emacs bug, for instance?

I dont recall we had firefox in 99. Even internet explorer , was it there ? good times.

Feels like my experience waiting for Microsoft or Jetbrains to fix bugs

Resolution: --- → DUPLICATE

That bug is older than half the audience here... Probably?

&gt; Updated version of patch. r=sfraser@netscape.com<p>Does that domain even exist anymore?

Also Firefox: not passing acid3 test

Holy shit, Firefox has been around for 25 years?

Sounds like maybe they should rewrite firefox in rust.