| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
The listbox content should always be rendered, even if there are no options available. Also, I was not able to reproduce this bug.
|
Sorry, something went wrong.
|
Reopening: Nitin (@49-22) can you post a reproduction? I was unable to reproduce this. If the test reproduction is only possible with Listbox.Content unmounted initially, then this can be closed. Listbox.Content should always be mounted. |
Sorry, something went wrong.
|
Yes, it’s reproducible only when Listbox.content is not mounted initially yet how about keeping an example to ensure even an uninformed AI agent or dev can avoid wasting time in debugging it. |
Sorry, something went wrong.
|
Ryan Bower (@R-Bower) Updated the examples to ensure what I missed is not missed by anyone else. |
Sorry, something went wrong.
|
Looks like signed commit was missing and DCO check was failing. |
Sorry, something went wrong.
mounts Signed-off-by: Nitin <nitin.nagamalla@gmail.com>
Signed-off-by: Nitin <nitin.nagamalla@gmail.com>
Signed-off-by: Nitin <nitin.nagamalla@gmail.com>
|
Ryan Bower (@R-Bower) is this good to go or anything pending from my side? |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Summary
Context
Reviewer feedback clarified that Listbox.Content is expected to always remain mounted, even when no options are available. This PR no longer changes core Listbox keyboard behavior for an initially unmounted content case. Instead, it documents the intended async-data pattern in the React docs.
Testing