This is a weird thing i noticed in chrome. if the user select a file and then select the same file again bu opening the file dialog again, chrome doesn’t fire the onchange event while firefox does.
anybody noticed it as well?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
This is a weird thing i noticed in chrome. if the user select a file and then select the same file again bu opening the file dialog again, chrome doesn’t fire the onchange event while firefox does.
anybody noticed it as well?
This is a known feature of Chrome and a quick Google on the topic will bring up some interesting discussions.
It makes sense to me that the
changeevent wouldn’t fire since nothing has changed (you’re selecting the same file)As for your question, what exactly are you asking? Are you looking for a way to change this behaviour or do you just want to know if we’ve noticed this as well?
If you want a way around this behaviour you can simply create a new file input in your Javascript and replace the previous one. This way your
changeevent is guarenteed to fire.