Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Guys,
we are experiencing following problem
Description of the Issue: After confirming a selection in a field within a table object, the display jumps horizontally back to the beginning (or to the left part) of the table. This behavior prevents effective work, as the user has to horizontally scroll back to the point of interest after each selection.
Steps to Reproduce:
Expected Behavior: After confirming a selection, the table display should remain at the position where the selection was made to facilitate efficient work.
Current Behavior: The display jumps back to the beginning of the table after each selection, requiring repeated horizontal scrolling and disrupting the workflow. This horizontal reset to the beginning of the table is particularly frustrating when working with wide tables.
It is worth mentioning that this behavior is very random. So far, we have not been able to identify a pattern. For some users, it never happens. For some, it happens in Chrome and in Edge. For others, it happens only in Chrome and not in Edge, or vice versa.
Environment:
Has anyone else experienced this issue? Are there any known workarounds or fixes? Any assistance would be greatly appreciated.
Thank you!
This is strange. I have tried here both in Chrome and Edge and I cannot reproduce the error. A wild guess is that maybe has something to do with JavaScript execution on the user's browser. Check the status or address bar for some warning or error message.
Also, contact Qlik support. They might have experienced this with other users in the past and have a solution.
Thank you for your response. It is indeed strange and not easy to reproduce. There are no error messages or any other warnings. Everything seems to be functioning normally as usual. For example, I personally experience this problem in Chrome, but in Edge, everything works fine form me.
A support case has already been created, but Qlik is referencing some unknown external factors, which might be true. However, I believe it should be in Qlik's interest to investigate this further.
Hi @Branislav , I know that you have case open with support and you have a meeting scheduled with my colleague @Omri_Amoyal tomorrow.
We also have not been able to replicate this; hopefully, the meeting will help us get forward.