Closed Bug 2016818 Opened 26 days ago Closed 19 days ago

applications filter field in settings no longer works

Categories

(Firefox :: Settings UI, defect, P2)

defect

Tracking

()

RESOLVED DUPLICATE of bug 2016820
149 Branch
Tracking Status
firefox-esr140 --- unaffected
firefox147 --- unaffected
firefox148 --- unaffected
firefox149 + fixed

People

(Reporter: soeren.hentzschel, Assigned: mkennedy)

References

(Regression)

Details

(Keywords: regression, Whiteboard: [recomp][fixed by bug 2016820])

After the conversion of the applications settings to the config-based prefs in bug 1972076, the filter field for applications no longer work. You can enter any nonsense and (almost?) all entries will still be displayed.

:mkennedy, since you are the author of the regressor, bug 1972076, could you take a look? Also, could you set the severity field?

For more information, please visit BugBot documentation.

Flags: needinfo?(mkennedy)
Assignee: nobody → mkennedy
Flags: needinfo?(mkennedy)
Severity: -- → S3
Priority: -- → P2
Whiteboard: [recomp]

Hmmm :soeren.hentzschel I'm unable to reproduce this on the latest Nightly. Can you provide a video of the behavior? Also if you can provide us with your operating system and version, that will help as well. Thanks!

Flags: needinfo?(soeren.hentzschel)

I tested it on macOS 26.2 and macOS 26.3.
Video: https://www.youtube.com/shorts/FzVkpxAnDd0

Flags: needinfo?(soeren.hentzschel)

The bug is marked as tracked for firefox149 (nightly). However, the bug still has low severity.

:pluk, could you please increase the severity for this tracked bug? If you disagree with the tracking decision, please talk with the release managers.

For more information, please visit BugBot documentation.

Flags: needinfo?(pluk)

Note: it's suspected that this bug is lower in severity because it only appears to happen in cases where there are custom file types beyond what's enabled by default. We're working on a solution fix. Clearing need info.

Flags: needinfo?(pluk)

I opened a patch to fix Bug 2016820. This work looks to have fixed this issue as well. Will resolve this once we can confirm.

I can verify that the issue is fixed in the latest Nightly. Thanks.

Status: NEW → RESOLVED
Closed: 19 days ago
Resolution: --- → FIXED
See Also: → 2016820
Whiteboard: [recomp] → [recomp][fixed by bug 2016820]
Depends on: 2016820
See Also: 2016820
Target Milestone: --- → 149 Branch
QA Whiteboard: [qa-triage-done-c150/b149]
Duplicate of bug: 2016820
Resolution: FIXED → DUPLICATE
You need to log in before you can comment on or make changes to this bug.