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
As you know, java.lang.Number is a superclass of Integer, Long, Short, [...].
Since the upgrade from 11.0.7 to 13.0.8 we face the issue that p:inputNumber defaults to 0 decimalPlaces when using a java.lang.Number (initial value null) as value.
This seems to happen because the check for integral, with a null value, tests for "isAssignableFrom(Integer.class)" etc.
Thus, it returns true, even though java.lang.Number can have decimalPlaces.
Reproducer
privateNumbernumber;
<p:inputNumbervalue="#{testView.number}" />
Expected behavior
No response
PrimeFaces edition
Community
PrimeFaces version
13.0.8
Theme
No response
JSF implementation
Mojarra
JSF version
2.3
Java version
11
Browser(s)
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
a PRO reported an issue related to InputNumberRenderer.isIntegral method. Will we add decimal type checks for Number type?
As you know, java.lang.Number is a superclass of Integer, Long, Short, [...].
Since the upgrade from 11.0.7 to 13.0.8 we face the issue that p:inputNumber defaults to 0 decimalPlaces when using a java.lang.Number (initial value null) as value.
This seems to happen because the check for integral, with a null value, tests for "isAssignableFrom(Integer.class)" etc.
Thus, it returns true, even though java.lang.Number can have decimalPlaces.
Reproducer
Expected behavior
No response
PrimeFaces edition
Community
PrimeFaces version
13.0.8
Theme
No response
JSF implementation
Mojarra
JSF version
2.3
Java version
11
Browser(s)
No response
The text was updated successfully, but these errors were encountered: