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

When using Groovy Postbuild's `manager.addShortText()` in Firefox, it will cause page misalignment in the build history list

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • core
    • Mac os monterey 12.3
      firefox version 100.0
      Jenkins version 2.332.3

      Using manager.addShortText($content) to show text in a build history list when the $content is long may cause page disorder , just like the photos attached.

       

      The timestamp could occupy a large blank and seems not aligned when using Firefox.

       

       

       

        1. firefox_1.jpg
          firefox_1.jpg
          141 kB
        2. image-2022-05-07-18-32-51-161.png
          image-2022-05-07-18-32-51-161.png
          137 kB
        3. image-2022-06-07-22-32-33-305.png
          image-2022-06-07-22-32-33-305.png
          85 kB
        4. image-2022-06-07-22-39-24-321.png
          image-2022-06-07-22-39-24-321.png
          146 kB
        5. image-2022-06-07-22-40-24-894.png
          image-2022-06-07-22-40-24-894.png
          149 kB
        6. new_1.png
          new_1.png
          84 kB
        7. on_safari.png
          on_safari.png
          127 kB
        8. plugin.png
          plugin.png
          70 kB
        9. safari_1.png
          safari_1.png
          259 kB
        10. viewpage.html
          65 kB

          [JENKINS-68427] When using Groovy Postbuild's `manager.addShortText()` in Firefox, it will cause page misalignment in the build history list

          C XY added a comment - - edited

          Is warnings-ng installed on the instance with the problem? 

          Does the page you're on include a reference to …/plugin/bootstrap5-api/css/jenkins-style.css?? in the source code???

           

          No.
          No.

           

           

          C XY added a comment - - edited Is warnings-ng installed on the instance with the problem?  Does the page you're on include a reference to …/plugin/bootstrap5-api/css/jenkins-style.css?? in the source code???   No. No.    

          Daniel Beck added a comment - - edited

          Is the Chinese localization plugin installed on both instances, or only the prod instance?

          (Unsure whether that'd be covered by "no obvious difference, asking just in case.)

          Daniel Beck added a comment - - edited Is the Chinese localization plugin installed on both instances, or only the prod instance? (Unsure whether that'd be covered by "no obvious difference, asking just in case.)

          C XY added a comment -

          I guess you mean this plugin. None of them installed this one.

          C XY added a comment - I guess you mean this plugin. None of them installed this one.

          Daniel Beck added a comment -

          To clarify, I am asking about https://plugins.jenkins.io/localization-zh-cn/

          Daniel Beck added a comment - To clarify, I am asking about https://plugins.jenkins.io/localization-zh-cn/

          C XY added a comment -

          Got it. The both instances are installed Localization: Chinese (Simplified)

          C XY added a comment - Got it. The both instances are installed Localization: Chinese (Simplified)

          Daniel Beck added a comment -

          I notice the build numbers are different in the "new_1" screenshot from the local machine.

          Could you use https://plugins.jenkins.io/next-build-number/ to set the build numbers to the ones from the prod instance to be as close as possible to the real environment with that as well?

          Daniel Beck added a comment - I notice the build numbers are different in the "new_1" screenshot from the local machine. Could you use https://plugins.jenkins.io/next-build-number/ to set the build numbers to the ones from the prod instance to be as close as possible to the real environment with that as well?

          C XY added a comment -

          I tried to use https://plugins.jenkins.io/next-build-number/ and the matter reproduced again at my local env. But there is a little difference that it did not reproduce until I set build number over 10000.

           

          C XY added a comment - I tried to use https://plugins.jenkins.io/next-build-number/ and the matter reproduced again at my local env. But there is a little difference that it did not reproduce until I set build number over 10000.  

          Daniel Beck added a comment -

          OK, so it looks like it's the following:

          5 digit build number + super long text badge + Firefox = problem

          That's a start

          Daniel Beck added a comment - OK, so it looks like it's the following: 5 digit build number + super long text badge + Firefox = problem That's a start

          C XY added a comment -

           

          C XY added a comment -  

          Jan Faracik added a comment -

          Builds widget got rewritten in https://www.jenkins.io/changelog-stable/2.479.1/ - and one area of focus was ensuring that content doesn't overflow in unexpected ways as it did in the classic widget.

          Would it possible for you to confirm if the issue is still around?

          Jan Faracik added a comment - Builds widget got rewritten in https://www.jenkins.io/changelog-stable/2.479.1/ - and one area of focus was ensuring that content doesn't overflow in unexpected ways as it did in the classic widget. Would it possible for you to confirm if the issue is still around?

            janfaracik Jan Faracik
            bignnonster C XY
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: