Skip to content
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

Drag & drop is slow to respond on slow devices #2974

Open
BenHenning opened this issue Mar 23, 2021 · 1 comment · May be fixed by #5677
Open

Drag & drop is slow to respond on slow devices #2974

BenHenning opened this issue Mar 23, 2021 · 1 comment · May be fixed by #5677
Assignees
Labels
bug End user-perceivable behaviors which are not desirable. Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet. Z-ibt Temporary label for Ben to keep track of issues he's triaged.

Comments

@BenHenning
Copy link
Member

Describe the bug
When using drag & drop on a slow device (e.g. Nexus 5X), the user has to tap & press for several seconds before getting the haptic feedback they've selected an item and can now drag it.

To Reproduce
Steps to reproduce the behavior:

  1. Use a slow device (such as a Nexus 5X)
  2. Navigate to the prototype exploration in a local developer build
  3. Play to the drag & drop interaction
  4. Try to drag items quickly
  5. Observe that they don't move at all due to a long tap & hold timeout

Expected behavior
Items should respond faster, or we should have instructions to make it clear that the user needs to tap and hold to drag. The latter may be more general-purpose, and mitigate even slower devices having a longer-than-expected delay. The key problem here is that it's unclear to the user that they're actually doing something correctly when trying to drag items.

Screenshots
N/A

Device

  • Device being used: Nexus 5X
  • SDK version: 27

Additional context
This was found while testing alpha MR2.

@BenHenning BenHenning added this to the Beta MR2 milestone Jun 11, 2022
@Broppia Broppia added Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). issue_type_infrastructure labels Jul 29, 2022
@BenHenning BenHenning added issue_type_bug Z-ibt Temporary label for Ben to keep track of issues he's triaged. and removed issue_type_infrastructure labels Sep 15, 2022
@BenHenning BenHenning removed this from the Beta MR2 milestone Sep 16, 2022
@seanlip seanlip added bug End user-perceivable behaviors which are not desirable. and removed issue_user_learner labels Mar 29, 2023
@adhiamboperes adhiamboperes added the Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet. label Jun 2, 2024
@BenHenning BenHenning added this to the 1.0 Global availability milestone Aug 29, 2024
@BenHenning BenHenning removed this from the 1.0 Global availability milestone Sep 25, 2024
@BenHenning
Copy link
Member Author

Note that this could be a big issue for some users, but we haven't had signal that users are running into this so deciding not to prioritize this for GA.

@manas-yu manas-yu self-assigned this Jan 4, 2025
@manas-yu manas-yu linked a pull request Jan 29, 2025 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug End user-perceivable behaviors which are not desirable. Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet. Z-ibt Temporary label for Ben to keep track of issues he's triaged.
Development

Successfully merging a pull request may close this issue.

5 participants