-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Count Record Opens Unintentionally if User Clicks in the Background While Results Are Being Fetched #474
Labels
Comments
R-Sourabh
added a commit
to R-Sourabh/inventory-count
that referenced
this issue
Oct 15, 2024
1 task
ymaheshwari1
added a commit
that referenced
this issue
Oct 25, 2024
Improved: added backdrop property which prevent triggering of any action(#474)
ymaheshwari1
moved this from 👀 In review
to ⏸️ Dev complete
in Digital Experience Platform
Oct 25, 2024
Issue verified in release v2.2.0 and found that issue is still replicating. Hence, reopening this issue. |
Will work on this ticket later as it has a lower priority. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Note
This can be observed on the slow network or with large dataset.
Current behavior
After results are fetched, the count record where the user clicked in the background opens automatically, disrupting the user's workflow.
Expected behavior
The user's click in the background during the fetching process should not trigger any action, and no count record should open unintentionally after the results are fetched.
Steps to reproduce the issue
Login the app using admin account.
Go to draft or assigned tab. Open the count and click back button.
While the results are being loaded, click anywhere in the background of the screen.
Once the results are fetched, observe that the count record corresponding to where the user clicked opens automatically.
Environment details
App version : v2.1.2
App environment : UAT
Additional information
https://jam.dev/c/20d823f3-5663-4c8f-a55b-5d4acfb111d3
The text was updated successfully, but these errors were encountered: