Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-6515

Dirty fields check does not work for all pages of a view

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.2.0-m1, 2.2
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-8001Checks not correctly cleared for dirty fields
      KULRICE-12486Dialog does not stop page change for dirty check
      KULRICE-7998Rewrite how Dirty Fields Work
      KULRICE-13958Checkbox dirty validation not working
      KULRICE-7851Dirty field indicator not working on Collections
      KULRICE-8870Cross-Page Validation
      KULRICE-9816New collection rows are not set to dirty
      KULRICE-5707Direct inquiry empty check not working and cancel on lightbox not working
      KULRICE-7625Dirty fields warning appears when returning from a lightbox
      KULRICE-12931Server side paging does not work when collection contains a field group
    • Rice Module:
      KRAD
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      On the kitchen sink if you fill in a value and then try to navigate away you will get the dirty fields prompt. However, if you do the same for one of the other pages, you do not get a prompt. Tested in Chrome.

        Activity

        Hide
        Eric Njogu (Inactive) added a comment -

        The kitchen sink does not appear to exhibit this behaviour in 2.2 branch. Trying the 2.0 trunk.

        Show
        Eric Njogu (Inactive) added a comment - The kitchen sink does not appear to exhibit this behaviour in 2.2 branch. Trying the 2.0 trunk.
        Hide
        Eric Njogu (Inactive) added a comment -

        It appears that validation for the first page is set up ok. Subsequent pages, which are fetched via ajax, are not. This is due to the temporary iframe that is created by the jquery form plugin - which is where the validation gets set up, yet is deleted when the ajax form submit finishes.

        Show
        Eric Njogu (Inactive) added a comment - It appears that validation for the first page is set up ok. Subsequent pages, which are fetched via ajax, are not. This is due to the temporary iframe that is created by the jquery form plugin - which is where the validation gets set up, yet is deleted when the ajax form submit finishes.
        Hide
        Eric Njogu (Inactive) added a comment -

        AJAX responses are loaded into a hidden div and are not set up for validation when the jquery dirty form plugin runs with default settings.

        Show
        Eric Njogu (Inactive) added a comment - AJAX responses are loaded into a hidden div and are not set up for validation when the jquery dirty form plugin runs with default settings.

          People

          • Assignee:
            Eric Njogu (Inactive)
            Reporter:
            Jerry Neal (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Structure Helper Panel