[
https://issues.jboss.org/browse/RF-12113?page=com.atlassian.jira.plugin.s...
]
Jan Papousek closed RF-12113.
-----------------------------
The issue is solved for rich:inputNumberSpinner, but it stays open for
rich:inputNumberSlider (RF-12387).
rich:inputNumberSpinner minValue and maxValue being ignored after
second request
--------------------------------------------------------------------------------
Key: RF-12113
URL:
https://issues.jboss.org/browse/RF-12113
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-input
Affects Versions: 4.2.0.Final
Environment: Windows 7 x64, Firefox/Waterfox v10.0.1, Chrome v17.0.963.83 m, IE8
64-bit v8.0.7601.17514
Reporter: Leo Higgins
Assignee: Luca Nardelli
Fix For: 4.3.0.Milestone1
When setting the value of the component to a value either below the specified minValue or
above the specified maxValue, the component correctly sets the value to either the
minValue or the maxValue.
On a subsequent request, however, the component does not set the value to the minValue or
the maxValue. This bug exists on all above browsers at the Richfaces showcase here:
http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=inputNu...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira