I believe your guess is correct.  We get some speed gains by not fully clearing the table, but this is a bug.  I hope to get to it in the next days, but these ones are tricky to track down.
Are there any blank lines or white space between the end of user B and the remnants of user A?


On Thu, May 15, 2014 at 2:19 AM, Ki Setargilop <gil@roadwarriors.ca> wrote:
Hi there,

My EGW version is 1.9.019.

I have an issue of having a previously selected responsible appeared in the
newly selected responsible in the infolog nextmatch index.

At first I selected user A in the responsible select box in the nextmatch
infolog index which returns 282 overdue todos. Afterwards, I selected user B
which returns 41 overdues todos. When I scroll down the table, it appears
that user A still exists in the filter of user B. My guess is that the
previous value of the ajax scroll is still there. How can I set the grid
scroll value to null, so that the previous value will not appear? I tried
tracing the code but it is very advanced in my level of expertise.



View this message in context: http://egroupware.219119.n3.nabble.com/How-to-make-the-nextmatch-grid-row-value-to-null-when-changing-responsible-tp3997798.html
Sent from the egroupware-developers mailing list archive at Nabble.com.

"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
eGroupWare-developers mailing list