Closed Bug 1756484 Opened 3 years ago Closed 3 years ago

Removing a search engine whilst preferences is open should not report an error

Categories

(Firefox :: Settings UI, defect, P3)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1758730

People

(Reporter: standard8, Assigned: standard8)

References

Details

We picked up on this when testing live language switching in bug 1750241 comment 2.

Easier STR:

  1. Start Firefox, open preferences, ensure the "General" section is selected.
  2. Open a second window and type in about:preferences (to get it in a second window).
  3. In the second window, navigate to the search shortcuts and remove an engine.

Expected Results

No errors.

Actual Results

Errors similar to bug 1750241 comment 1 or:

17:49:57.780 Uncaught 
Exception { name: "NS_ERROR_UNEXPECTED", message: "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsITreeSelection.select]", result: 2147549183, filename: "chrome://browser/content/preferences/search.js", lineNumber: 472, columnNumber: 0, data: null, stack: "remove@chrome://browser/content/preferences/search.js:472:27\nobserve@chrome://browser/content/preferences/search.js:359:23\nnotifyAction@resource://gre/modules/SearchUtils.jsm:223:20\nremoveEngine@resource://gre/modules/SearchService.jsm:2011:17\n", location: XPCWrappedNative_NoHelper }
search.js:472
    remove chrome://browser/content/preferences/search.js:472
    observe chrome://browser/content/preferences/search.js:359
    notifyAction resource://gre/modules/SearchUtils.jsm:223
    removeEngine resource://gre/modules/SearchService.jsm:2011
    InterpretGeneratorResume self-hosted:1475
    AsyncFunctionNext self-hosted:685
Summary: Removing a search engine whilst preferences is open should not result in an error → Removing a search engine whilst preferences is open should not report an error
Severity: -- → S4
Priority: -- → P3

This is being fixed in bug 1758730.

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