Roji Philip

> Sounds like the case got missed in [the original implementation](https://github.com/Expensify/Expensify/issues/387117). We agreed in Slack we def want to handle this though. @joekaufmanexpensify Thanks for the clarification. Can we also...

> Just to confirm @rojiphil, this one will be an entirely backend issue? Looks like a BE issue to me but it depends on the feedback for the comment [here](https://github.com/Expensify/App/issues/53034#issuecomment-2512138592)....

Cool. Now that we have a consensus on the way ahead, I think we can make this issue as `internal`. Meanwhile, I am unassigning myself here but will stay subscribed...

> can you review the proposals here please? Sorry for the delay here. Will review today.

Thanks for all your proposals. @nyomanjyotisa Adding style.boxShadowNone does not seem to be the way to go as the blue frame on search icon will not be displayed when needed...

Sure. Will update today

> What I understand is that we don't want to see the focus effect in our case on any mWeb platform (touch devices, narrow layout) - meaning to have consistency...

> Have you tried my alternative solution with `pressableRef?.current?.blur()`? It prevents the navigation issue, blurs the search icon only when the user selects it and ensures the search icon is...

Thanks for all your proposals. @nyomanjyotisa [proposal](https://github.com/Expensify/App/issues/52128#issuecomment-2460365285) with alternative solution and as mentioned [here](https://github.com/Expensify/App/issues/52128#issuecomment-2481711830) LGTM. 🎀👀🎀 C+ reviewed

> The selected proposal involves focusing and then blurring the button, which feels redundant and more like a workaround. In my proposal, we can prevent the button from being focused...