Comment 4 for bug 1238979

We need design guidance on that, subscribed them.

In my opinion, darkening the results and blocking the dash is not the best way to solve our problem.

The problem is: *new* results might come in just while the user is trying to tap an item, ending in opening something new that was not seen yet.

The proposed solution makes the dash *current* results unresponsive and visually darkened until the search process ends. Please notice that this might take a lot of time, in case of not fast or unreliable connections or depending on device speed. This brings a couple of disadvantages, one is visually cluttering the interface, resulting in elements changing colours continuously, another one is wasting all the time during searches, because the user cannot interact thus leaving no choice than to wait for an indeterminate amount of time that could be long, as said, depending on different factors (I think this can be frustrating).
Sometimes also the user might be happy with one of the current results already displayed, but this way he/she cannot interact and has to wait till the end of the search and eventually redo the previous search to open the item he/she liked.
At the same time, when the darkening goes away, are we sure the user will try to tap on the first item thinking only the darkening changed and not also the content?

I propose a new solution for those *new* results coming in after the search is completed: we make those new, and not the current, inactive for a small amount of time, like 100-200ms (while even animating them into the view, if we like). This way, not only we aim and really fix the issue of tapping a new item which just popped in on screen, but also we both not visually clutter the dash with colour changes and always keep the dash responsive in case the user find his/herself satisfied with a currently displayed results and does not care about the pending search any more.

What you guys think?