-
-
Notifications
You must be signed in to change notification settings - Fork 260
[composite] Avoid skipping missing elements in listRef
#3066
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
Conversation
commit: |
Bundle size report
|
✅ Deploy Preview for base-ui ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The change makes sense in theory. 👍
But am I missing something?
It looks like on the docs deployed on master the described problem does not exist (tested Combobox and Autocomplete). 🤷
|
@LukasTy you sure? It happens for me on master Screen.Recording.2025-10-28.at.7.55.59.pm.mov |
|
@atomiks Yes, on Chrome running MacOS 18 it works like this: Screen.Recording.2025-10-28.at.12.50.52.movAlso tested Safari and Firefox... 🤷 |
|
Right, the bug occurs if you focus the input without clicking it, so it doesn't open yet |
Whoops. My bad, I skipped that part. 🙈 |
Tweak to #2604
Because of virtualization, missing elements in the
listRefarray shouldn't be skipped when determining the active index. In the virtualized demo, pressing ArrowUp lands on the 31st item (last item in the virtual window) instead of the 10,000th item.