4 ms·

The Firefox bug tracker is full of thousands of bugs with some sitting there for 10-15 years. I’d like to see way more focus on cleaning these up than new featu

The Firefox bug tracker is full of thousands of bugs with some sitting there for 10-15 years. I’d like to see way more focus on cleaning these up than new features and UI changes.

blfr 3y ago
No. Local translations and blurred video calls background are (unironically) very important.
riquito 3y ago
Every big software will end up with open bugs as old as itself
- 0xcde4c3db 3y ago
  Usually either that, or they have a policy of closing bugs that are "too old" with no attempt to reproduce or otherwise follow up.
  - ilyt 3y ago
    Then inevitable "wait, this still happens" And someone closing new reports of same bug as duplicate of one that is closed, despise it still happening...
- user3939382 3y ago
  It's not about the age of the oldest bug on its own per se, it's the number of them juxtaposed with their releases where fixing bugs is priority 0.
tmpX7dMeXU 3y ago
No. This is the reality of mature software.
deleted 3y ago
[deleted]
jeroenhd 3y ago
With translations built in, I have one less reason to use Chrome. There are a few old open bugs, the oldest Firefox bug seemingly being 9 years old, and is about pdf.js not automatically rendering hyperlinks as clickable. There are a few UI/usability bugs in the list, but most old bugs seem to be meta bugs linking several blocking issues, or features being completed part by part. Firefox may lack engineering power to keep up with Chrome (especially after firing all of those Rust devs), but in terms of bugs I don't think they're doing all that badly. It's not like fixing "Consider to process DOMLinkAdded event using animation frame callback + setTimeout(, 0)" is going to help them gain any market share.
- user3939382 3y ago
  > There are a few old open bugs When I tried to look, the results maxed out at 10,000 and the bug tracker stopped being able to respond or sort by date. I wouldn't call 10,000+ "a few" it sounds like you're downplaying it for some reason. Should releases include hundreds of closed bugs? No. But there could be a couple dozen. Mozilla has the resources to do that. Look at their release notes. A handful of security fixes (good) and otherwise nothing about bug fixes. These are not the release notes of an organization prioritizing software quality.
  - cpmsmith 3y ago
    Is 1278 enough for you? They don't list every single bug in the release notes; that would be a full time job on its own. https://bugzilla.mozilla.org/buglist.cgi?f1=cf_status_firefox118&list_id=16734592&o1=equals&query_format=advanced&v1=fixed&order=bug_status%2Cpriority%2Cassigned_to%2Cbug_id&limit=0 https://bugzilla.mozilla.org/buglist.cgi?f1=cf_status_firefo...
maccard 3y ago
https://bugs.chromium.org/p/chromium/issues/list?sort=opened https://bugs.chromium.org/p/chromium/issues/list?sort=opened scanning throuhg this list there are oodles of bugs there that are 10-15 years old too.

The Firefox bug tracker is full of thousands of bugs with some sitting there for 10-15 years. I’d like to see way more focus on cleaning these up than new features and UI changes.

blfr 3y ago

No. Local translations and blurred video calls background are (unironically) very important.

riquito 3y ago

Every big software will end up with open bugs as old as itself

0xcde4c3db 3y ago
Usually either that, or they have a policy of closing bugs that are "too old" with no attempt to reproduce or otherwise follow up.
- ilyt 3y ago
  Then inevitable "wait, this still happens" And someone closing new reports of same bug as duplicate of one that is closed, despise it still happening...
user3939382 3y ago
It's not about the age of the oldest bug on its own per se, it's the number of them juxtaposed with their releases where fixing bugs is priority 0.

tmpX7dMeXU 3y ago

No. This is the reality of mature software.

deleted 3y ago

[deleted]

jeroenhd 3y ago

With translations built in, I have one less reason to use Chrome. There are a few old open bugs, the oldest Firefox bug seemingly being 9 years old, and is about pdf.js not automatically rendering hyperlinks as clickable. There are a few UI/usability bugs in the list, but most old bugs seem to be meta bugs linking several blocking issues, or features being completed part by part. Firefox may lack engineering power to keep up with Chrome (especially after firing all of those Rust devs), but in terms of bugs I don't think they're doing all that badly. It's not like fixing "Consider to process DOMLinkAdded event using animation frame callback + setTimeout(, 0)" is going to help them gain any market share.

user3939382 3y ago
> There are a few old open bugs When I tried to look, the results maxed out at 10,000 and the bug tracker stopped being able to respond or sort by date. I wouldn't call 10,000+ "a few" it sounds like you're downplaying it for some reason. Should releases include hundreds of closed bugs? No. But there could be a couple dozen. Mozilla has the resources to do that. Look at their release notes. A handful of security fixes (good) and otherwise nothing about bug fixes. These are not the release notes of an organization prioritizing software quality.
- cpmsmith 3y ago
  Is 1278 enough for you? They don't list every single bug in the release notes; that would be a full time job on its own. https://bugzilla.mozilla.org/buglist.cgi?f1=cf_status_firefox118&list_id=16734592&o1=equals&query_format=advanced&v1=fixed&order=bug_status%2Cpriority%2Cassigned_to%2Cbug_id&limit=0 https://bugzilla.mozilla.org/buglist.cgi?f1=cf_status_firefo...

maccard 3y ago

https://bugs.chromium.org/p/chromium/issues/list?sort=opened https://bugs.chromium.org/p/chromium/issues/list?sort=opened scanning throuhg this list there are oodles of bugs there that are 10-15 years old too.