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

Global Search Input Loses Characters During Typing #5348

Open
2 tasks done
bnewman-tech opened this issue Feb 14, 2024 · 0 comments
Open
2 tasks done

Global Search Input Loses Characters During Typing #5348

bnewman-tech opened this issue Feb 14, 2024 · 0 comments

Comments

@bnewman-tech
Copy link

TanStack Table version

8.12.0

Framework/Library version

18.2.0

Describe the bug and the steps to reproduce it

Issue
While typing in the global search input, some characters intermittently disappear as if the table is attempting to filter results before fully capturing the new search term. This behavior results in the search term being reset to a previous state, omitting the newly typed characters. The issue manifests at varying speeds, depending on how quickly the user types, leading to an inconsistent user experience.

Steps to Reproduce
Navigate to the page with the mantine-react-table component.
Focus on the global search input field.
Begin typing a search term rapidly.
Observe that some characters typed do not appear in the input field and are missing from the search term.

Your Minimal, Reproducible Example - (Sandbox Highly Recommended)

https://stackblitz.com/github/tanstack/table/tree/main/examples/react/filters?embed=1&theme=light

Screenshots or Videos (Optional)

Kapture.2024-02-14.at.13.40.54.mp4

In the video you can see that an "l" was removed really quick as I was typing the next "l"

Do you intend to try to help solve this bug with your own PR?

No, because I do not know how

Terms & Code of Conduct

  • I agree to follow this project's Code of Conduct
  • I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant