Uploaded image for project: 'RichFaces'
  1. RichFaces
  2. RF-12113

rich:inputNumberSpinner minValue and maxValue being ignored after second request

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 4.2.0.Final
    • Fix Version/s: 4.2.3.CR1, 4.3.0.M1
    • Component/s: component-input
    • Labels:
      None
    • Environment:

      Windows 7 x64, Firefox/Waterfox v10.0.1, Chrome v17.0.963.83 m, IE8 64-bit v8.0.7601.17514

    • Steps to Reproduce:
      Hide

      1. Navigate to Richfaces showcase for rich:inputNumberSpinner
      2. Set the value in either spinner to a negative value and click out of the component
      3. Set the value in the same spinner to a negative value again, note the value stays negative and isn't set to 0 (the default minValue)

      Show
      1. Navigate to Richfaces showcase for rich:inputNumberSpinner 2. Set the value in either spinner to a negative value and click out of the component 3. Set the value in the same spinner to a negative value again, note the value stays negative and isn't set to 0 (the default minValue)

      Description

      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=inputNumberSpinner&skin=blueSky

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  tritibo Luca Nardelli
                  Reporter:
                  dealmaster Leo Higgins
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  6 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: