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

Active Choices elements are not rendered correctly

      I am not sure if this is bug or configuration issues.

      I was not able to find any resource around this or any associated bugs.

      I have corporate installed and configured Jenkins 2.263.3 with Active Choices (uno-choice) 2.1

      Form with select drop down rendering with Name and drop down on same line and description under the drop down list:

      I also have separate Jenkins 2.227.3 with Active Choices (uno-choice) 2.5.6

      Same form rendering each item on a new line ...

      The only difference that I can see in source code that first one is designed using TABLE HTML elements and second using DIV

      Is this bug or configuration issues?

      I want to have on my separate instance UI like on the first screenshot.

          [JENKINS-65521] Active Choices elements are not rendered correctly

          Markus Winter added a comment -

          See the Jenkins changelog about the change from tables to div. So this is by design. It has no impact on functionality.

          Markus Winter added a comment - See the Jenkins  changelog about the change from tables to div. So this is by design. It has no impact on functionality.

          Areg added a comment - - edited

          Yes I have seen that, how that does not affect another instance?

          Or when they will upgrade it UI will change too?

          It has an impact on UI and how elements are aligned - users are not happy.

          Could Plug-in vendor fix that?

          Areg added a comment - - edited Yes I have seen that, how that does not affect another instance? Or when they will upgrade it UI will change too? It has an impact on UI and how elements are aligned - users are not happy. Could Plug-in vendor fix that?

          Areg added a comment -

          Even if it changed to use DIV instead of TABLE the view should remain same.

          Areg added a comment - Even if it changed to use DIV instead of TABLE the view should remain same.

          That appears to be a bug vrtareg , thanks for reporting.

          mwinter69 assessment is correct too. There was a recent change in Jenkins' layout that caused this issue.

          >Could Plug-in vendor fix that?

          There is no vendor here vrtareg . The plug-in is maintained by volunteers. You are welcome to submit a pull request if you have time to volunteer helping with this bug. Or if you have urgency, I think CloudBees and other companies accept paid work to fix bugs like this.

          Otherwise we should fix it in one of the next development iterations if we have time (again, this is volunteer, every developer here has family, friend $work, life, etc, and cannot always work fixing the issues as soon as they'd like )

          Cheers

          Bruno

          Bruno P. Kinoshita added a comment - That appears to be a bug vrtareg , thanks for reporting. mwinter69 assessment is correct too. There was a recent change in Jenkins' layout that caused this issue. >Could Plug-in vendor fix that? There is no vendor here vrtareg . The plug-in is maintained by volunteers. You are welcome to submit a pull request if you have time to volunteer helping with this bug. Or if you have urgency, I think CloudBees and other companies accept paid work to fix bugs like this. Otherwise we should fix it in one of the next development iterations if we have time (again, this is volunteer, every developer here has family, friend $work, life, etc, and cannot always work fixing the issues as soon as they'd like ) Cheers Bruno

          Areg added a comment -

          Hi kinow

          Thanks a lot confirming that it is a bug.

          I will be happy to have a look - could you point me to the correct repo for the source as I am not sure which one is the actual one for uno-choice now...

          Regards,

          Areg

          Areg added a comment - Hi kinow Thanks a lot confirming that it is a bug. I will be happy to have a look - could you point me to the correct repo for the source as I am not sure which one is the actual one for uno-choice now... Regards, Areg

          Sure thing Areg, the sources are hosted here: https://github.com/jenkinsci/active-choices-plugin

          Thank you!

          Bruno P. Kinoshita added a comment - Sure thing Areg, the sources are hosted here: https://github.com/jenkinsci/active-choices-plugin Thank you!

          Areg added a comment -

          Thanks kinow

          Looks like it is over my capabilities

          I will leave it to someone with better knowledge of the code.

          Areg added a comment - Thanks kinow Looks like it is over my capabilities I will leave it to someone with better knowledge of the code.

          Areg added a comment -

          Hi

          Just wondering if anyone was able to have a look to this?

          Areg added a comment - Hi Just wondering if anyone was able to have a look to this?

          Hi vrtareg

          I haven't done any progress in fixing this issue, but I think this is the same issue ioannis pointed to me in a meeting some weeks ago. For a form with 20+ parameters, the list of parameters gets really long with the new layout.

          It would be better if we had it the old way, so that the UI was more compact. We can ask the Jenkins core devs if it would be possible, but if not, the last resort would be to override the CSS styles of Jenkins in Active Choices. Not hard, but also not elegant (and also brittle).

          Bruno

          Bruno P. Kinoshita added a comment - Hi vrtareg I haven't done any progress in fixing this issue, but I think this is the same issue ioannis pointed to me in a meeting some weeks ago. For a form with 20+ parameters, the list of parameters gets really long with the new layout. It would be better if we had it the old way, so that the UI was more compact. We can ask the Jenkins core devs if it would be possible, but if not, the last resort would be to override the CSS styles of Jenkins in Active Choices. Not hard, but also not elegant (and also brittle). Bruno

            kinow Bruno P. Kinoshita
            vrtareg Areg
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: