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

The bread crumb navigation on the top of the job is not responding after clicking Apply

    • Jenkins 2.235

      After clicking the Apply to save the job configuration the the top breadcrumb navigation that allows editing and moving to the parent view is no longer functional. When clicking on it nothing happens. This started happening after may be 2.226 

          [JENKINS-62065] The bread crumb navigation on the top of the job is not responding after clicking Apply

          Daniel Beck added a comment - - edited

          This started happening after may be 2.226

          2.230 actually. It still works on 2.229.

          Daniel Beck added a comment - - edited This started happening after may be 2.226 2.230 actually. It still works on 2.229.

          Daniel Beck added a comment -

          romenrg FYI

          Daniel Beck added a comment - romenrg FYI

          Just tested it locally and it seems this only happens if the user has scrolled. Going back to the top of the page the breadcrumb links are clickable.

          Doing some further research, I discovered the issue. The notification-bar div has opacity 0 but it is still being displayed and, when moved down, that div is located right above the breadcrumb, preventing clicks. I'm working on a fix, to set display to "none" when the alert disappears.

          Romen Rodriguez-Gil added a comment - Just tested it locally and it seems this only happens if the user has scrolled. Going back to the top of the page the breadcrumb links are clickable. Doing some further research, I discovered the issue. The notification-bar div has opacity 0 but it is still being displayed and, when moved down, that div is located right above the breadcrumb, preventing clicks. I'm working on a fix, to set display to "none" when the alert disappears.

          This bug has been addressed in the following PR: https://github.com/jenkinsci/jenkins/pull/4696

          Romen Rodriguez-Gil added a comment - This bug has been addressed in the following PR:  https://github.com/jenkinsci/jenkins/pull/4696

            romenrg Romen Rodriguez-Gil
            sgabriel Samuel Gabriel
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: