With the steps provided it's pretty easy for me to reproduce on a Samsung S7, I think this is a general issue.
Thinking further about it, the search widget uses a lot of already existing code and features. Tapping the widget is similar to tapping a link to be opened in the browser. With this in mind I've tried to open an external link in Firefox while having the tab tray opened and indeed the "issue" also manifests in this situation - https://drive.google.com/open?id=1K2IXb72t0LwYH8ss-s5N00HrtbmmygfM
Another scenario in which the previous state hinders the functionality is when the settings menu is displayed.
Tapping the search widget (or tapping on a link to be opened in Firefox) opens a new tab for searching but does not close the menu - https://drive.google.com/open?id=1KK3GVIrXC9JhhnZRlGK-VQeirKqO7o4Y
There might be other similar scenarios.
Given that this is not a recent regression and a fix for the search widget scenario would extend to other related functionality (like opening an external link) I think we need to thread carefully but the solution should not be hard.
The way I see it, we need to explicitly:
- close the tab tray
- close the keyboard
- close the menu
- close other stuff??
When the user puts the app in background so to have a cleaner state when the user returns,
Or when the user opens a new tab, before actually opening the tab (Scenario I think closer to the issue described in this ticket)
What do you guys think?