This problem is very urgent. My application wont work without a workaround.
I think it might be that the "first"-Attribute of the scrollable table is still computed wrong.
Meanwhile I found out that it is definitely the key from the selection that is computed wrong.
Is it possible to fix that in 3.2.2?
If you'll check carefully - you'll find the jira tickets opened for selection bugs.
We do not closes not fixed ones.
And if you think your one is differs from the opened - just add it also to jira(with corresponding test case and steps attachment).
could you tell me the tickets which are opended regarding this bug?
I did not found an open ticket, only closed ones.
Thanks a lot
check the tickets assigned to Konstantin Mishin.