-
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
auto-unmasking #397
Comments
hey, i have a proposal : wouldn't be nice to have the option to set up an alternative input instead (like myInput becomes myInputFormatted) while to original input is converted to a hidden one? this way, formatting is only a "ui" feature, and everything is transparent for the backend (where we can use simple formatting for numbers, dates, etc...) and since the original id/name is preserved, any script listing to or requesting the value will get the proper, unformatted value. |
I would also like to see this feature in future release. The flatpickr plugin also has the same feature |
exactly, and it's very convenient :-) |
Anything new about this common feature? Thanks. :) |
The fake UI / Hidden input as suggest by @lekoala can be added. |
@nosir it is a valid concern. probably it would be best to copy classes (and favor classes over ids) from the original input if you want to enable this feature. it's a minor tradeoff in my opinion. good practice is about using classes over ids anyway. |
I use .NET. On form submit, it sends both values. It should delete the masked form before, right? |
Hello,
I would like to propose a feature: auto-unmasking. When activating auto-unmasking the value of an input-element will return the raw value from cleave instead of the actually displayed value.
The problem with the current solution (getRawValue/setRawValue) is that there are frameworks that register change listeners on input elements which in turn read/write the value field. In such a case it is not possible to call getRawValue/setRawValue instead. In this case it would be nice to get the raw value from
document.getElementById('myelement').value
.Regards, Alex
The text was updated successfully, but these errors were encountered: