-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[BUG] - Bug when input type is file. #2311
Comments
Same here, any solutions? |
I am experiencing the same issue. For now, I am using a regular input element and styled it the same. |
Same issue in 2.2.10 |
same issue in v2.3.6 |
This seems to be an issue since If I force
Don't actually do the above in production, it does give a warning that values should not be null, they should be There are some related tickets to this issue in the issue tracker: |
Thanks for fix. |
NextUI Version
2.2.92.4.1Describe the bug
When using the input component with file type, I observed that on the first click to choose a file, the selected file is logged as "undefined" in the console. However, on the second attempt, the correct file information is logged
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
Click the "Choose File" button to open the file dialog.
On the first click, notice that the selected file is logged as "undefined" in the console.
On the second click, the correct file information is logged.
Expected behavior
The file input value should be cleared consistently on each click to ensure that the correct file information is logged on the first attempt.
Screenshots or Videos
INPUT-FILETYPE-ERROR-01.mp4
Operating System Version
windows 11
Browser
Edge
The text was updated successfully, but these errors were encountered: