Bugfix for #48378 - Resetting value of input element to fix Chrome-specific issue
What does this MR do?
Bugfix for #48378 (closed). It sets the value of the input element to null after input[type=file]
's change event is triggered so that user can select the same image twice for their Avatar
Are there points in the code the reviewer needs to double check?
Check if removing the return value affects anything. I believe the return value was being discarded till now
Why was this MR needed?
Bugfix for #48378 (closed)
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added -
Tests added for this feature/bug - Conform by the code review guidelines
-
Has been reviewed by a UX Designer -
Has been reviewed by a Frontend maintainer -
Has been reviewed by a Backend maintainer -
Has been reviewed by a Database specialist
-
-
Conform by the merge request performance guides -
Conform by the style guides -
If you have multiple commits, please combine them into a few logically organized commits by squashing them -
Internationalization required/considered -
End-to-end tests pass ( package-and-qa
manual pipeline job)
What are the relevant issue numbers?
Edited by Chirag