Closed Bug 1240695 Opened 8 years ago Closed 3 years ago

Flicker in Default Search Engine drop-down on deleting engines from about:preferences#search

Categories

(Firefox :: Search, defect, P5)

Product:
Firefox
Component:
Search
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox42 --- affected
firefox43 --- affected
firefox44 --- affected
firefox45 --- affected
firefox46 --- affected
firefox-esr38 --- affected
firefox65 --- affected
firefox66 --- affected
firefox67 --- affected
firefox68 --- affected

People

(Reporter: adalucinet, Unassigned)

Details

(Whiteboard: [fxsearch]) 

Reproducible with 44.0RC (Build ID: 20160118143821), latest Aurora 45.0a2 and Nightly 46.0a1 (from 2016-01-18)
Affected platforms: Windows 7 x64, Windows 10 x86, Mac OS X 10.9.5 and Ubuntu 14.04 x86

Steps to reproduce:
1. Launch Firefox and go to about:preferences#search
2. Randomly delete One-click search engines

Expected result: No flicker.
Actual result: Flicker in Default Search Engine drop-down.

Additional notes:
1. Also reproducible with 40.0RC - not a recent regression.
Also reproducible with Nightly 38.0a1 2015-02-01 - not a regression.
put pretty low as it's such an edge case and it's lower than our other quality work.  we'd gladly take a patch from a contributor
Priority: -- → P5
Whiteboard: [fxsearch]
Still reproducible with 65.0a1 (2018-12-10), 66.0a1 (2019-01-03), 65.0b8.
status-firefox65: --- → affected
status-firefox66: --- → affected
Summary: [intermittent] Flicker in Default Search Engine drop-down while deleting engines via about:preferences#search → Flicker in Default Search Engine drop-down on deleting engines from about:preferences#search

This issue is also reproducible if you change the search engine order by drag and drop.

status-firefox67: --- → affected
status-firefox68: --- → affected
Severity: normal → S4

I've just been trying this by hiding the section in-between and re-testing. I can't reproduce a flicker now.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.