Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-64429

<f:number clazz="positive-number"> broken with extra FormValidation

    XMLWordPrintable

    Details

    • Similar Issues:
    • Released As:
      2.277

      Description

      if your Jelly uses

       <f:number clazz="positive-number" min="1" step="1" default="1"/>
      

      and also has a doCheck method then an initial failure validation is never cleared.

      to reproduce, unpack the provided test project and build it. (this will use a jenkins version prior to table to div)
      start the plugin with `mvn hpi:run` and go to the http://localhost:8080/jenkins/configure page.
      Observe that there is a validation error for the "My Field" in "JENKINS-64429" section.
      Change the value so that it is valid (to 1) and tab out of the field
      Observe that the validation error clears.

      stop the Jenkins process.
      clean the work and target (rm -fr work/ target/)
      build with a newer version of jenkins core (mvn hpi:run -Djenkins.version=2.270) and go to the http://localhost:8080/jenkins/configure page.
      Observe that there is a validation error for the "My Field" in "JENKINS-64429" section.
      Change the value so that it is valid (to 1) and tab out of the field
      Observe that the validation warning does not disappear

        Attachments

          Issue Links

            Activity

            teilo James Nord created issue -
            teilo James Nord made changes -
            Field Original Value New Value
            Assignee James Nord [ teilo ]
            teilo James Nord made changes -
            Description if your Jelly uses

            {noformat}
             <f:number clazz="positive-number" min="1" step="1" default="1"/>
            {noformat}

            and also has a {{doCheck}} method then an initial failure validation is never cleared.
            if your Jelly uses

            {noformat}
             <f:number clazz="positive-number" min="1" step="1" default="1"/>
            {noformat}

            and also has a {{doCheck}} method then an initial failure validation is never cleared.

            to reproduce, unpack the provided test project and build it. (this will use a jenkins version prior to table to div)
            start the plugin with `hpi:run` and go to the /configure page.
            Observe that there is a validation error for the "My Field" in "JENKINS-64429" section.
            Change the value so that it is valid (to 1) and tab out of the field
            Observe that the validation error clears.

            stop the Jenkins process.
            clean the work and target (rm -fr work/ target/)
            build with a newer version of jenkins core ({{mvn hpi:run -Djenkins.version=2.270}}) and go to the /configure page.
            Observe that there is a validation error for the "My Field" in "JENKINS-64429" section.
            Change the value so that it is valid (to 1) and tab out of the field
            Observe that the validation warning does not disappear
            teilo James Nord made changes -
            Description if your Jelly uses

            {noformat}
             <f:number clazz="positive-number" min="1" step="1" default="1"/>
            {noformat}

            and also has a {{doCheck}} method then an initial failure validation is never cleared.

            to reproduce, unpack the provided test project and build it. (this will use a jenkins version prior to table to div)
            start the plugin with `hpi:run` and go to the /configure page.
            Observe that there is a validation error for the "My Field" in "JENKINS-64429" section.
            Change the value so that it is valid (to 1) and tab out of the field
            Observe that the validation error clears.

            stop the Jenkins process.
            clean the work and target (rm -fr work/ target/)
            build with a newer version of jenkins core ({{mvn hpi:run -Djenkins.version=2.270}}) and go to the /configure page.
            Observe that there is a validation error for the "My Field" in "JENKINS-64429" section.
            Change the value so that it is valid (to 1) and tab out of the field
            Observe that the validation warning does not disappear
            if your Jelly uses

            {noformat}
             <f:number clazz="positive-number" min="1" step="1" default="1"/>
            {noformat}

            and also has a {{doCheck}} method then an initial failure validation is never cleared.

            to reproduce, unpack the provided test project and build it. (this will use a jenkins version prior to table to div)
            start the plugin with `mvn hpi:run` and go to the http://localhost:8080/jenkins/configure page.
            Observe that there is a validation error for the "My Field" in "JENKINS-64429" section.
            Change the value so that it is valid (to 1) and tab out of the field
            Observe that the validation error clears.

            stop the Jenkins process.
            clean the work and target (rm -fr work/ target/)
            build with a newer version of jenkins core ({{mvn hpi:run -Djenkins.version=2.270}}) and go to the http://localhost:8080/jenkins/configure page.
            Observe that there is a validation error for the "My Field" in "JENKINS-64429" section.
            Change the value so that it is valid (to 1) and tab out of the field
            Observe that the validation warning does not disappear
            teilo James Nord made changes -
            Description if your Jelly uses

            {noformat}
             <f:number clazz="positive-number" min="1" step="1" default="1"/>
            {noformat}

            and also has a {{doCheck}} method then an initial failure validation is never cleared.

            to reproduce, unpack the provided test project and build it. (this will use a jenkins version prior to table to div)
            start the plugin with `mvn hpi:run` and go to the http://localhost:8080/jenkins/configure page.
            Observe that there is a validation error for the "My Field" in "JENKINS-64429" section.
            Change the value so that it is valid (to 1) and tab out of the field
            Observe that the validation error clears.

            stop the Jenkins process.
            clean the work and target (rm -fr work/ target/)
            build with a newer version of jenkins core ({{mvn hpi:run -Djenkins.version=2.270}}) and go to the http://localhost:8080/jenkins/configure page.
            Observe that there is a validation error for the "My Field" in "JENKINS-64429" section.
            Change the value so that it is valid (to 1) and tab out of the field
            Observe that the validation warning does not disappear
            if your Jelly uses

            {noformat}
             <f:number clazz="positive-number" min="1" step="1" default="1"/>
            {noformat}

            and also has a {{doCheck}} method then an initial failure validation is never cleared.

            to reproduce, unpack the provided test project and build it. (this will use a jenkins version prior to table to div)
            start the plugin with `mvn hpi:run` and go to the http://localhost:8080/jenkins/configure page.
            Observe that there is a validation error for the "My Field" in "JENKINS-64429" section.
            Change the value so that it is valid (to 1) and tab out of the field
            Observe that the validation error clears.

            stop the Jenkins process.
            clean the work and target (`rm -fr work/ target/`)
            build with a newer version of jenkins core ({{mvn hpi:run -Djenkins.version=2.270}}) and go to the http://localhost:8080/jenkins/configure page.
            Observe that there is a validation error for the "My Field" in "JENKINS-64429" section.
            Change the value so that it is valid (to 1) and tab out of the field
            Observe that the validation warning does not disappear
            teilo James Nord made changes -
            Description if your Jelly uses

            {noformat}
             <f:number clazz="positive-number" min="1" step="1" default="1"/>
            {noformat}

            and also has a {{doCheck}} method then an initial failure validation is never cleared.

            to reproduce, unpack the provided test project and build it. (this will use a jenkins version prior to table to div)
            start the plugin with `mvn hpi:run` and go to the http://localhost:8080/jenkins/configure page.
            Observe that there is a validation error for the "My Field" in "JENKINS-64429" section.
            Change the value so that it is valid (to 1) and tab out of the field
            Observe that the validation error clears.

            stop the Jenkins process.
            clean the work and target (`rm -fr work/ target/`)
            build with a newer version of jenkins core ({{mvn hpi:run -Djenkins.version=2.270}}) and go to the http://localhost:8080/jenkins/configure page.
            Observe that there is a validation error for the "My Field" in "JENKINS-64429" section.
            Change the value so that it is valid (to 1) and tab out of the field
            Observe that the validation warning does not disappear
            if your Jelly uses

            {noformat}
             <f:number clazz="positive-number" min="1" step="1" default="1"/>
            {noformat}

            and also has a {{doCheck}} method then an initial failure validation is never cleared.

            to reproduce, unpack the provided test project and build it. (this will use a jenkins version prior to table to div)
            start the plugin with `mvn hpi:run` and go to the http://localhost:8080/jenkins/configure page.
            Observe that there is a validation error for the "My Field" in "JENKINS-64429" section.
            Change the value so that it is valid (to 1) and tab out of the field
            Observe that the validation error clears.

            stop the Jenkins process.
            clean the work and target ({{rm -fr work/ target/}})
            build with a newer version of jenkins core ({{mvn hpi:run -Djenkins.version=2.270}}) and go to the http://localhost:8080/jenkins/configure page.
            Observe that there is a validation error for the "My Field" in "JENKINS-64429" section.
            Change the value so that it is valid (to 1) and tab out of the field
            Observe that the validation warning does not disappear
            teilo James Nord made changes -
            Attachment screenshot-1.png [ 53584 ]
            teilo James Nord made changes -
            Description if your Jelly uses

            {noformat}
             <f:number clazz="positive-number" min="1" step="1" default="1"/>
            {noformat}

            and also has a {{doCheck}} method then an initial failure validation is never cleared.

            to reproduce, unpack the provided test project and build it. (this will use a jenkins version prior to table to div)
            start the plugin with `mvn hpi:run` and go to the http://localhost:8080/jenkins/configure page.
            Observe that there is a validation error for the "My Field" in "JENKINS-64429" section.
            Change the value so that it is valid (to 1) and tab out of the field
            Observe that the validation error clears.

            stop the Jenkins process.
            clean the work and target ({{rm -fr work/ target/}})
            build with a newer version of jenkins core ({{mvn hpi:run -Djenkins.version=2.270}}) and go to the http://localhost:8080/jenkins/configure page.
            Observe that there is a validation error for the "My Field" in "JENKINS-64429" section.
            Change the value so that it is valid (to 1) and tab out of the field
            Observe that the validation warning does not disappear
            if your Jelly uses

            {noformat}
             <f:number clazz="positive-number" min="1" step="1" default="1"/>
            {noformat}

            and also has a {{doCheck}} method then an initial failure validation is never cleared.

            to reproduce, unpack the provided test project and build it. (this will use a jenkins version prior to table to div)
            start the plugin with `mvn hpi:run` and go to the http://localhost:8080/jenkins/configure page.
            Observe that there is a validation error for the "My Field" in "JENKINS-64429" section.
            Change the value so that it is valid (to 1) and tab out of the field
            Observe that the validation error clears.

            stop the Jenkins process.
            clean the work and target ({{rm -fr work/ target/}})
            build with a newer version of jenkins core ({{mvn hpi:run -Djenkins.version=2.270}}) and go to the http://localhost:8080/jenkins/configure page.
            Observe that there is a validation error for the "My Field" in "JENKINS-64429" section.
            Change the value so that it is valid (to 1) and tab out of the field
            Observe that the validation warning does not disappear

             !screenshot-1.png|thumbnail!
            teilo James Nord made changes -
            Attachment JENKINS-64429.zip [ 53585 ]
            teilo James Nord made changes -
            Assignee James Nord [ teilo ]
            amuniz Antonio Muñiz made changes -
            Link This issue is related to JENKINS-64651 [ JENKINS-64651 ]
            fqueiruga Félix Queiruga Balado made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            fqueiruga Félix Queiruga Balado made changes -
            Status In Progress [ 3 ] In Review [ 10005 ]
            fqueiruga Félix Queiruga Balado made changes -
            Assignee Félix Queiruga Balado [ fqueiruga ]
            timja Tim Jacomb made changes -
            Link This issue is duplicated by JENKINS-64651 [ JENKINS-64651 ]
            markewaite Mark Waite made changes -
            Released As 2.277
            Resolution Fixed [ 1 ]
            Status In Review [ 10005 ] Closed [ 6 ]

              People

              Assignee:
              fqueiruga Félix Queiruga Balado
              Reporter:
              teilo James Nord
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: