Welcome to Codidact Meta!
Codidact Meta is the "town hall" (meta-discussion site) for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Empty search performed automatically on reaching the search page
On desktop the search button in the top bar of each page opens a dialog box where a search term can be entered. On mobile (or on a narrow or zoomed desktop window) there is less room in the top bar so search is instead an option in the hamburger menu (3 horizontal lines) at the top right of the page. This option takes you to a search page with an empty search field ready to perform a search. This is all as intended.
However, the search page performs a search before you interact with it, so it displays all posts (the result of an empty search string). In addition to serving no purpose for the person searching, this also seems to cause unnecessary work for the server[1], and to be potentially confusing for some users. Would it be better for the initial search page to show no results until the user performs a search?
-
I don't know how much delay this adds to the user loading the search page, or whether it would add noticeable delay to other users at times of high server load. For me testing today it seems to add between 1 and 3 seconds delay depending on the size of the community. ↩︎
0 comment threads