Bug 1913193 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

**Found in**
* Nightly 131.0a1;

**Affected versions**
* Nightly 131.0a1;

**Affected platforms**
* Ubuntu 22;
* macOS 14;
* Windows 11; 

**Preconditions**
* Have browser.urlbar.scotchBonnet.enableOverride to TRUE

**Steps to reproduce**
1. From a new tab, open the unified desktop search button dropdown by clicking on it (down arrow)
2. Close the dropdown by clicking on the button again
3. Repeat the above steps (if necessary)

**Expected result**
* The dropdown is correctly closed and reopened.

**Actual result**
* The dedicated search button is stuck in the address bar, it can’t be reopened. Address bar dropdown is not opened when starting to type into urlbar. This persists in new tabs, but not in new windows.
* Browser Console warning: SearchEngine: getSubmission: searchTerms is empty! 2 SearchEngine.sys.mjs:1428:23

**Regression range**
* Not a regression. 

**Additional notes**
* Closing the dropdown by clicking outside of it or by pressing Escape will not reproduce this issue.
**Found in**
* Nightly 131.0a1;

**Affected versions**
* Nightly 131.0a1;

**Affected platforms**
* Windows 11; 

**Preconditions**
* Have browser.urlbar.scotchBonnet.enableOverride to TRUE

**Steps to reproduce**
1. From a new tab, open the unified desktop search button dropdown by clicking on it (down arrow)
2. Close the dropdown by clicking on the button again
3. Repeat the above steps (if necessary)

**Expected result**
* The dropdown is correctly closed and reopened.

**Actual result**
* The dedicated search button is stuck in the address bar, it can’t be reopened. Address bar dropdown is not opened when starting to type into urlbar. This persists in new tabs, but not in new windows.
* Browser Console warning: SearchEngine: getSubmission: searchTerms is empty! 2 SearchEngine.sys.mjs:1428:23

**Regression range**
* Not a regression. 

**Additional notes**
* Closing the dropdown by clicking outside of it or by pressing Escape will not reproduce this issue.

Back to Bug 1913193 Comment 0