You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the mouseout event, inputmask resets the input's placeholder to whatever placeholder it had when inputmask was first initialised.
If the placeholder on the input was changed afterwards, the new placeholder gets lost.
When hovering and then leaving the text input, its placeholder is set back to "old placeholder".
Expected behaviour (IMO) would be that if the input's placeholder is changed by something other than inputmask, inputmask should remember that placeholder as the placeholder to reset to (from taking a short look at the code, i believe that'd be in the originalPlaceholder attribute of the inputmask object).
Alternatively, there should be an option to manually set the originalPlaceholder to avoid this issue.
Inputmask version: I could reproduce this on both 5.0.9 and 5.0.10-beta.8
OS: Windows 10
Browser: I could reproduce this on both Firefox and Chrome
The text was updated successfully, but these errors were encountered:
On the
mouseout
event, inputmask resets the input's placeholder to whatever placeholder it had when inputmask was first initialised.If the placeholder on the input was changed afterwards, the new placeholder gets lost.
Minimum reproducible example:
When hovering and then leaving the text input, its placeholder is set back to "old placeholder".
Expected behaviour (IMO) would be that if the input's placeholder is changed by something other than inputmask, inputmask should remember that placeholder as the placeholder to reset to (from taking a short look at the code, i believe that'd be in the
originalPlaceholder
attribute of theinputmask
object).Alternatively, there should be an option to manually set the
originalPlaceholder
to avoid this issue.Inputmask version: I could reproduce this on both 5.0.9 and 5.0.10-beta.8
OS: Windows 10
Browser: I could reproduce this on both Firefox and Chrome
The text was updated successfully, but these errors were encountered: