Problem
Front's search function (Ctrl+F) overrides the browser's native search and doesn't work reliably—it fails to find text strings visible on the page, particularly those containing underscores.
Request
Provide a setting to disable Front's search override and use the browser's native search function instead.
Please, don't override native browser features, especially if it's not to enhance them, e.g. to workaround the lack of virtualization; It's poor UX right now.
Hello,
Sorry to hear that the control+f feature is not working as you expect.
Today's behavior is the same as the Desktop app, where a 'control+f' now triggers a search local to the selected conversation thread only. This is to make sure you can search for a specific text in a long conversation thread.
Before this, the browser search would search only on things visible. Which was missing results in collapsed conversations.
Could you share more about what you are trying to search and what is not working? Like:
Are you trying to search for something in the entire window or only in the selected conversation thread? If the former, could you share more about your use case?
Can you give examples of search queries not working well (ideally a screenshot and an example of what you would have expected)
Thank you!