I have added a text search field in my search page here > hidden link but there are some issues in the functionality.
1. In every browser and mobile device that i tested, I click on the field but suddenly the field is not clicked and I must click again in order to start typing.
2. In firefox, there is one more issue. When you start typing in the field, the search of the browser opens ( ctr+f). Please check my screenshot > hidden link
Link to a page where the issue can be seen: hidden link
Hello and thank you for contacting the Toolset support.
Please check if this issue appears when:
- Only Toolset plugins are activated. It will tell us if there is an interaction issue with another plugin.
- The theme is set to a WordPress default like Twenty Fourteen. It will tell us if there is an interaction issue with your theme.
If the problem disappears, start activating one at a time to track where the incompatibility is produced.
I did all the actions that you suggested to me but the issues are still remaining.
Would you allow me to take a copy of your website for further analysis locally?
First, I thought that the issue comes from the touch script in the Twenty-nineteenth theme. So, I created a custom code to disable this script. This has fixed the issue on my local install, but it did not on the staging site.
I kept debugging and from what I could gather so far, I think that the issue is on the view pagination configuration, I am not sure as I can't reproduce the issue on my local setup.
The view on the page is configured to automatically paginate after 2s, and to use infinite scrolling for pagination. Each time it paginates it recreates the search form.
The page and the view were created using the Blocks editor, but after installing the "Classic Editor" plugin, the page has switched to use the classic editor, and there is no way to reconfigure the view.
On my local install, I deactivated the "Classic Editor" plugin in order to edit the page with the blocks editor. I selected the view and changed the configuration to "Pagination enabled with manual transition and AJAX". Check the screenshot hidden link
I tried to do the same on the staging site but I could not. The page is still opened with the classic editor even after deactivating the "Classic Editor" plugin. I would suspect that a server-level caching is preventing the page to be opened with the blocks editor.
Depending on how you would like to continue building your pages(Blocks or Classic editor), I'll suggest that you build the view similarly. I mean:
- If you want to build pages using the classic editor, create the view using the Toolset legacy editor.
- If you want to build pages using the blocks editor, you can create the view using blocks or the Toolset legacy editor.
I hope this helps. Let me know if you have any questions.
My issue is resolved now. Thank you!
