Closed Bug 1769570 Opened 2 years ago Closed 2 years ago

[Intermittent] Infobar not displayed on idle when Firefox default engine is removed

Categories

(Firefox :: Search, defect, P3)

Firefox 102
Desktop
All
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox101 --- affected
firefox102 --- affected

People

(Reporter: phorea, Assigned: mcheang)

References

Details

Attachments

(1 file)

+++ This bug was created as a follow-up of Bug #1759207 +++

Description
With the fix of Bug #1759207, we have encountered a few cases in which the default engine removal would be successful but the infobar will not show. This was observed only in the 5' idle time scenario after the search-config was updated.

Affected versions

  • Beta 101
  • Nightly 102

Affected platforms

  • all

Steps to reproduce

  1. Create a profile for a region/localization that has google.com as Firefox set default engine.
  2. Have a search-config update that contains a removal of a Firefox set engine, e.g. google.com
  3. Have the search-config update in pipeline. (changes are brought from RS, but not yet applied)
  4. Wait for at least 5 minutes - computer is idle

Expected result
Default engine is removed and Infobar is displayed stating that the google.com engine is replaced.

Actual result
Default engine is removed, but Infobar is not displayed every time (happens intermittently)

Regression range

  • Not a regression
Has STR: --- → yes
Assignee: nobody → mcheang
Priority: -- → P3

Redid the STR on Win10 and Mac11 with no success into reproducing the issue anymore. 15/15 successful attempts on beta101. I'll mark it as WFM for now and retry again at a later date on a machine that also reproduced this issue.

@Petruta, give it a few tries when possible.

Status: NEW → RESOLVED
Closed: 2 years ago
Flags: needinfo?(petruta.rasa)
Resolution: --- → WORKSFORME

(In reply to Adrian Florinescu [:aflorinescu] from comment #1)

Redid the STR on Win10 and Mac11 with no success into reproducing the issue anymore. 15/15 successful attempts on beta101. I'll mark it as WFM for now and retry again at a later date on a machine that also reproduced this issue.

@Petruta, give it a few tries when possible.

Same results on 101RC on a machine that previously reproduced this (intermittently).

Flags: needinfo?(petruta.rasa)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: