34 comments
@ZiggyTheHamster @brion no beef but also that’s an interesting role to earn millions a year from @brion And it was basically a one-line fix. https://phabricator.services.mozilla.com/D187418 @brion The best part is that the person who provided the commit to fix it had had their Mozilla Bugzilla account for like 4 days; it's only like a month old at this point. Bravo to them finally fixing an issue that has plagued us since before Phoenix 0.1 was even a thing! This is just an all-around awesome thing to see! @brion The fact that the bug reporting tool is, I guess, still the same is also amazing. I'm always glad any software tool lasts longer than 5 years before there is another one that does exactly the same but misses the feature you relied on. https://www.bugzilla.org/blog/2023/08/26/bugzilla-celebrates-25-years/ @brion makes me wonder if it could be fun to write fixes for ancient yet prevalent bugs, as a hobby. not sure if I will, but the idea is curious. Also there is no pressure: the bug has been there for 20 years, you can take a year of occasionally looking at code to fix it and people will likely still enjoy :3 @brion@bikeshed.vibber.net wait is this from before it was called firefox @brion fucking finally, this bug is super annoying, i run into it constantly
@brion dang, and I thought it'd been a long time when it took over 10 years for Fink's PR 66 to get merged... @brion Oh my god. This has been one of the most frustrating things about Firefox for *years* |
@brion Amazing (I have definitely been annoyed by this bug!)