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

Different behavior in InputNumber Clientside Validation #4392

Closed
mertsincan opened this Issue Jan 10, 2019 · 0 comments

Comments

Projects
None yet
1 participant
@mertsincan
Copy link
Member

mertsincan commented Jan 10, 2019

Reported By PRO User;

we use an InputNumber component with decimalSeperator and two decimal places:

<p:inputNumber id="number" value="#{test.number}" decimalSeparator="," decimalPlaces="2" converter="#{tkform.converter.float}">
	<p:clientValidator event="change" />
</p:inputNumber>
<p:commandButton id="submit" value="Submit" action="#{test.submit}" type="submit" validateClient="true" update="@form" />

On this component, we validate clientside on javascript "change"-event and on submit through button click.

Now we have a custom clientside validator:

PrimeFaces.validator['Between'] = {
	validate: function(element, value) {
		...
	}
}

By entering "12,12", the value parameter differs depending on whether it comes from change event (it is "12.12") or button click (it is "12,12").

@mertsincan mertsincan added this to the 6.3 milestone Jan 10, 2019

@mertsincan mertsincan self-assigned this Jan 10, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment