You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I often open the app on the call history tab as I most often call someone that I already called recently, or to call back someone that's just called me. However if I want to call someone that's not in there I naturally use the search to search that contact but then I get an empty result as it searches only in the tab I'm in. So I have to go to the contact tab and then search again. This feels like a rather counter-intuitive behaviour, at least for my workflow.
While I'm sure some user like the current behaviour, it would be nice to have the option to make the search bar a global search across all tabs.
The text was updated successfully, but these errors were encountered:
This "global search" behaviour requested here is by the way the default behaviour of the main dial app on stock android and lineage os and so I expect this is what users would be most used to (including myself, and I was rather confused by the behaviour of the Simple Contact / Dial app in that respect)
By the way, should this issue be opened here or in the Simple-Dialer repo? They both seem to rely on the same back-end for contact view / search so I'm not sure.
I often open the app on the call history tab as I most often call someone that I already called recently, or to call back someone that's just called me. However if I want to call someone that's not in there I naturally use the search to search that contact but then I get an empty result as it searches only in the tab I'm in. So I have to go to the contact tab and then search again. This feels like a rather counter-intuitive behaviour, at least for my workflow.
While I'm sure some user like the current behaviour, it would be nice to have the option to make the search bar a global search across all tabs.
The text was updated successfully, but these errors were encountered: