Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
auto-unmasking
See original GitHub issueHello,
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
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I use .NET.
On form submit, it sends both values.
It should delete the masked form before, right?
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.