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

Navigating back, then forward, from a job configuration causes loss of config data

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Fixed
    • Component/s: core
    • Labels:
    • Environment:
      Chrome version 27.0.1453.116 on MacOS 10.6.8.
    • Similar Issues:

      Description

      1. Open a job configuration that has a conditional build step defined in it, with the Chrome browser (Firefox does not show this problem).
      2. Click the back button to navigate away from the config.
      3. Click forward to go back to the config.
      4. The conditional build step settings will be blank/default, but all other job configuration remains correct.

      This is a really nasty bug, I've had a number of users accidentally break their configs without realizing it, because if you save after this happens you lose the conditional build step settings. Luckily the Job Config History plugin makes it easy for us to undo this.

        Attachments

          Issue Links

            Activity

            Hide
            danielbeck Daniel Beck added a comment -

            Similar issues affect multiple browsers, so removing Chrome from title.

            Given the number of issues that appear to be duplicates, raising priority.

            Show
            danielbeck Daniel Beck added a comment - Similar issues affect multiple browsers, so removing Chrome from title. Given the number of issues that appear to be duplicates, raising priority.
            Hide
            jglick Jesse Glick added a comment -

            Lazy-loaded form fragments are added to the DOM by some JavaScript hooks. Probably these are being run on initial page load but not when revisiting a page, and the browser is throwing out the modified DOM.

            Show
            jglick Jesse Glick added a comment - Lazy-loaded form fragments are added to the DOM by some JavaScript hooks. Probably these are being run on initial page load but not when revisiting a page, and the browser is throwing out the modified DOM.
            Hide
            jglick Jesse Glick added a comment -

            I suspect the most appropriate fix is just to add some JS to block the back/forward buttons while on such a page.

            Show
            jglick Jesse Glick added a comment - I suspect the most appropriate fix is just to add some JS to block the back/forward buttons while on such a page.
            Hide
            recampbell Ryan Campbell added a comment -

            rsandell has a PR in review for this issue.

            Show
            recampbell Ryan Campbell added a comment - rsandell has a PR in review for this issue.
            Hide
            danielbeck Daniel Beck added a comment -

            Fixed towards 2.15.

            Show
            danielbeck Daniel Beck added a comment - Fixed towards 2.15.

              People

              • Assignee:
                rsandell rsandell
                Reporter:
                owenmehegan Owen Mehegan
              • Votes:
                4 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: