Bug 1889116 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.

### Prerequisites
* Use a fresh profile.

### Steps to reproduce

1. On the homescreen, tap the search engine icon drop-down menu.
2.a) Select Tabs/Bookmarks/ History search engine.
3.a) Observe the selected search icon from the search bar.

2.b) Select Bing/Amazon/DuckDuckGo/eBay/Wikipedia engine.
3.b) Observe the selected search icon from the search bar.

### Expected behavior
The search icon is successfully updated according to the selected search engine.

### Actual behavior
a) There is no icon displayed when selecting one of the Tabs/Bookmarks/History option. (reproducible only with
b) The first selected search icon remains displayed for all the next selected engines.

### Device information

* Firefox version: Firefox Nightly 126 (2024-04-02)
* Android device model: Samsung A32 (Android 13) , Oppo A15s (Android 10), Xiaomi mi8 lite (Android 10) 

### Any additional information?
* This issue is a recent regression: Last good build (2024-04-01) - First Bad Build (2024-04-02)
### Prerequisites
* Use a fresh profile.

### Steps to reproduce

1. On the homescreen, tap the search engine icon drop-down menu.
2.a) Select Tabs/Bookmarks/ History search engine.
3.a) Observe the selected search icon from the search bar.

2.b) Select Bing/Amazon/DuckDuckGo/eBay/Wikipedia engine.
3.b) Observe the selected search icon from the search bar.

### Expected behavior
The search icon is successfully updated according to the selected search engine.

### Actual behavior
a) There is no icon displayed when selecting one of the Tabs/Bookmarks/History option. (reproducible only in dark mode)
b) The first selected search icon remains displayed for all the next selected engines.

### Device information

* Firefox version: Firefox Nightly 126 (2024-04-02)
* Android device model: Samsung A32 (Android 13) , Oppo A15s (Android 10), Xiaomi mi8 lite (Android 10) 

### Any additional information?
* This issue is a recent regression: Last good build (2024-04-01) - First Bad Build (2024-04-02)

Back to Bug 1889116 Comment 0