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

When a field is refreshed that triggers a progressive disclosure condition, the check for progressive disclosure is not triggered

    Details

    • Type: Bug Fix Bug Fix
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-6340ajax progressive disclosure / refresh are broken
      KULRICE-13424Fill AFT Gap: Kitchen Sink: Progressive Disclosure
      KULRICE-7996Progressive disclosure and refresh within table not working
      KULRICE-5835changes to a field populated by fieldAttributeQuery.returnFieldMapping doesn't trigger progressive rendering based on that value
      KULRICE-7221Progressive disclosure within collections throwing exception
      KULRICE-7590Support for progressive disclosure and component refresh on content elements
      KULRICE-11448Create Automated Functional Test for KRAD Library Client Responsiveness Progressive Disclosure added recently
      KULRICE-6568Progressive Disclosure server side improvements
      KULRICE-7672Conditional Refresh Performance
      KULRICE-7460KRAD test drive/sample app - add a conditional refresh example, disabling an editable input field
    • Rice Module:
      KRAD
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      I discovered this issue while doing some testing with the new #np binding prefix on the agenda editor.

      If you have a field that progressively discloses another field, and then that field (the trigger field) is refreshed (by another condition) when the field refreshes the progressive disclose condition is not checked. If the field changes we need the condition to be rechecked and the disclosed content to be shown or hidden.

      This seems similar to another issue we had where the fields we populated from an ajax query or lookup where not triggering the progressive disclosure checks. I had to trigger the change event in code. It seems the browsers don't fire change events when a value is changed programmatically.

      Just a note the same problem would occur if the refreshed field was suppose to trigger a refresh check itself.

      Not exactly sure the solution. One possibility is to look through the refreshed content to pick up fields and trigger the change event. However, this has some problems. One the value might not have actually changed. So it could send a refresh call when it is not needed. Second the refreshed content could be a big collection, so we would be going through triggering change events on several fields that probably don't even have a condition. There might be a way we can query to determine if the field has a listener before we trigger.

      The testing I did was not checked in as it was not actually part of the agenda. So we will need to recreate the situation in the kitchen sink.

        Activity

        There are no comments yet on this issue.

          People

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

            Dates

            • Created:
              Updated:

              Structure Helper Panel