From 514f6b6cd5a9f541256306bd45d50d4f4389a634 Mon Sep 17 00:00:00 2001
From: LucasGGamerM <moshidon.app@gmail.com>
Date: Sun, 24 Nov 2024 11:43:35 -0300
Subject: [PATCH] feat: readd search on long press search icon

---
 .../joinmastodon/android/fragments/HomeFragment.java  | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/mastodon/src/main/java/org/joinmastodon/android/fragments/HomeFragment.java b/mastodon/src/main/java/org/joinmastodon/android/fragments/HomeFragment.java
index 735df67d0..22b189b08 100644
--- a/mastodon/src/main/java/org/joinmastodon/android/fragments/HomeFragment.java
+++ b/mastodon/src/main/java/org/joinmastodon/android/fragments/HomeFragment.java
@@ -266,6 +266,17 @@ public class HomeFragment extends AppKitFragment implements AssistContentProvide
 	}
 
 	private boolean onTabLongClick(@IdRes int tab){
+		if(tab==R.id.tab_search){
+			if(currentTab!=R.id.tab_search){
+				// MOSHIDON: I don't know why using setCurrentTab leads to visual glitches
+				// when initially loading the fragment. This solves it somehow
+				onTabSelected(R.id.tab_search);
+				tabBar.selectTab(R.id.tab_search);
+			}
+			searchFragment.openSearch();
+			return true;
+		}
+
 		if(tab==R.id.tab_profile){
 			ArrayList<String> options=new ArrayList<>();
 			for(AccountSession session:AccountSessionManager.getInstance().getLoggedInAccounts()){