The search bar at the top is now appearing much later as the page loads. I find this frustrating. In the past, you could start typing into the search box as soon as it appeared. Now you have to wait for the page to be completely rendered. (I am on an iPhone using Chrome.)
In fact it is the rest of the page that loads faster the search bar.
In the past the whole page was remaining blank until everything is rendered. We recently changed it so that we display whatever we can as soon as possible, and the rest appears later.
"We recently changed it so that we display whatever we can as soon as possible, and the rest appears later."
So why is the form for the advanced search appearing at last? It is added to the page by a script? More generally, what is "the rest"?
From the pure U.I. point of view, It is very unpleasant to see elements of the bottom appear before elements of the top, especially if the element of the top is needed. It gives a feeling of unnecessarily waiting. Although the waiting time would be the same the other way, the feel is different since users tend to understand a page "from top to bottom".
> So why is the form for the advanced search appearing at last?
It doesn't appear last for me. And shouldn't appear last for you either... If you can make a video of how it shows up for you, that might help.
> More generally, what is "the rest"?
Basically elements that are rendered with Angular Material will take more time to display. The language dropdown is one of those elements. The buttons as well.
> From the pure U.I. point of view, It is very unpleasant to see elements of the bottom
> appear before elements of the top, especially if the element of the top is needed.
This is something I noted in the pull request. In my case it was more an impression that something was broken for a short time, but I understand the feeling, that there's something disturbing about the delayed rendering.
However, having used the website for a couple of weeks now with this delayed rendering, I personally don't feel disturbed by it anymore. But that's maybe influenced by two things:
1) The search bar is most of the time rendered pretty fast for me. I can notice the delay, but it's really just a fraction of a second.
2) I don't search very often when I'm on Tatoeba. Most of the time I look at the Wall and in such case, I'm actually quite fine that the Wall messages appear first and the search bar is rendered later.
Perhaps a compromise would be to revert to the previous behavior (i.e. all blank until everything is rendered) on specific pages. I would guess the homepage and the search results would be the main candidates.
But I would very much like more feedback on this delayed rendering before we proceed on changing things. Does this annoy anyone else, or did most people get used to it?
I’m using Firefox. I do notice a delay between the moment the green empty banner shows and the search fields appear. The delay is between one and two seconds. I think we can work on reducing the delay, I already have some ideas I wrote in a Github issue: https://github.com/Tatoeba/tatoeba2/issues/1891
The issue for me is not so much when the elements are displayed, but (a) how long I have to wait to start typing into the advanced search form (which I use more than the regular search because I prefer random ordering to shortest-first) and (b) whether the elements on the page resize themselves while I'm trying to do an operation (such as scrolling to the top). Before the recent change, I could count on being able to type into the advanced search form (the same way that DostKaplan could count on being able to type into the regular search form) even when it was loading. Now that's no longer the case.
On a similar subject, I generally have multiple tabs (maybe around 10) open in Chrome on an Android tablet or phone, and one of them is generally a Tatoeba advanced search page that I want to reuse in order to perform a new advanced search. When I reactivate it, I find that the page tries to redo the last advanced search, which I no longer care about, before I can perform the new search. This doesn't happen when I use Firefox on Windows. I'm not sure whether this is behavior that is under our control, but if the browser didn't try to redo the old search, I wouldn't need to care as much about the rendering order. Also, searching on a tablet would be faster for me in general. The load on the server might also be reduced, making searches faster for everyone.
[not needed anymore- removed by CK]
It would be more useful if the submit button posts the results to a _named_ window/tab. That way, the results always appear in a separate, same window on submission of the search request. As it is right now, the results appear in the same window/tab as the cut-down version of the Advanced Search page. This means that I can't simply "backspace" once to quickly do another search if I had been hitting "next" multiple times to view the results of my previous search. And doing all this in Chrome on an iPhone means I don't have a bookmark right on the screen that I can access easily (like you can on a desktop or laptop). To get to the bookmark involves several taps. Displaying the results in a named window would help.
Also, what must I choose on the cut-down version of the advanced search page to NOT show results that don't have translations in the target language? Example:
Search text: rendezvous
Results: I see English sentences without Turkish translations.