Closed Bug 1450239 Opened 6 years ago Closed 6 years ago

[about:preferences]"Sorry! There are no results in Options for..." is still present even after you click on another section.

Categories

(Firefox :: Settings UI, defect, P1)

61 Branch
defect

Tracking

()

VERIFIED FIXED
Firefox 61
Tracking Status
firefox-esr52 --- unaffected
firefox59 --- unaffected
firefox60 --- unaffected
firefox61 --- verified

People

(Reporter: obotisan, Assigned: jaws)

References

Details

(Keywords: regression)

[Affected versions]:
- Nightly 61.0a1

[Affected platforms]:
- Windows 10 x64
- Ubuntu 16.04 x64
- macOS 10.13

[Steps to reproduce]:
1. Navigate to about:preferences
2. Input an invalid therm in the search bar (eg. sdadasd)
3. Click on another section (eg. Home, Search, Privacy & Security etc.)
4. Observe behaviour.

[Expected result]:
- The Search Results page and the message "Sorry! There are no results in Options for..." disappears and the options for the selected section are displayed. 

[Actual result]:
- The Search Results page and the message "Sorry! There are no results in Options for..." still appears and the options for the selected section is displayed underneath it. 

[Regression range]:
- last good build: 2018-03-20
- first bad build: 2018-03-21
- mozregression concluded that bug 1446657 - Refactor preferences search code to remove flickering and scrollbar appearing/disappearing. might the one that caused this issue.
Flags: needinfo?(jaws)
I will add a test for this in bug 1449658. Keeping needinfo open to make sure that I come back to this.
Will be fixed by the patch in bug 1449658.
Assignee: nobody → jaws
Status: NEW → ASSIGNED
Flags: needinfo?(jaws)
Priority: -- → P1
Depends on: 1449658
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 61
I verified the fix using latest Nightly on Windows 10x64, Ubuntu 16.04 x64 and macOS 10.13 and the bug is not reproducing anymore. I will mark this bug as verified fixed.
Status: RESOLVED → VERIFIED
Flags: in-qa-testsuite+
You need to log in before you can comment on or make changes to this bug.