-
Notifications
You must be signed in to change notification settings - Fork 752
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
InputMask: optional part does now work correctly #6469
Comments
Please always check the migration guide before you create a ticket ;) https://primefaces.github.io/primefaces/9_0/#/../migrationguide/9_0 sorry, only checked the last example :D |
I will look into this but we moved to a new component as the previous InputMask had so many bugs including problems with |
To fix it right now add |
validate="false" does not solve it. if i enter 44 for the areacode this is translated to 44__ such that the folloowing error is thrown: '44__' must be a number between -2147483648 and 2147483647 Example: 9346 |
this is because error is of course due to the fact that areaCode should be an integer here! |
using slotChar="" is a partial workaround which works in our case because we do not have case where two or more digits are required at least. this should give you also a hint for the bugfix. |
you have to clear the slotChars before doing the validation |
I have a fix. working on it now and writing and integration test. |
@melloware with the change from the april to latest snapshot, p:inputMask is not working anymore correctly at least for mask with optional cases.
example:
previously it was working well as follows:
can you please check and fix this.
when i try to save, it clears the inputMask fields (see screenshot)
The text was updated successfully, but these errors were encountered: