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

Date picker (and other widgets) still work when a field is disabled

    Details

    • Similar issues:
      KULRICE-13117Disable Date Picker Control when the field is disabled
      KULRICE-12616Date Picker icon still has color even when disabled
      KULRICE-7211Default datePicker widget disabled property to disabled property on control
      KULRICE-9666custom search attribute with non-ranged date picker doesn't render the widget
      KULRICE-5888Date picker not accessible by keyboard
      KULRICE-7141Verify that Disabled for datepicker and lookup widgets can be disabled client-side when disabled on the fly
      KULRICE-7999Dirty fields not being updated when using a date picker
      KULRICE-11751Field groups and date picker being doubled in labs proposal
      KULRICE-5639Within the date-picker widget, there are previous and next buttons. In IE, when hovering over these, the images flicker on and off. When clicking, nothing happens.
      KULRICE-7261Datepicker - InputField not properly updated when format is "mm-dd-yy" and input field is bound to a Date
    • Epic Link:
    • Rice Module:
      KRAD
    • Sprint:
      2.5.0-m1 Sprint 1, 2.5.0-m1 Sprint 2
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      When a field becomes disabled, the date picker still works and changes the value. Likely there would be an issue with other widgets as well (quickfinder). The widgets should become hidden when the field is disabled.

      Need to address:

      • date picker
      • quick finder (make sure inquiry remains enabled)
      • spinner
      • text area (allow text area to be expanded/popped up in read only mode)

      Also to do:

      • Add these cases to KRAD Library -> Client Responsiveness -> Disable (done)
      • Create QA Jira to update the AFT to verify that these cases work correctly

        Issue Links

          Activity

          Hide
          Adam Campbell (Inactive) added a comment -

          Created RICEQA-355 to modify AFTs for KULRICE-12615 and KULRICE-12616.

          Show
          Adam Campbell (Inactive) added a comment - Created RICEQA-355 to modify AFTs for KULRICE-12615 and KULRICE-12616 .
          Hide
          Jerry Neal (Inactive) added a comment -

          Jeff,

          Can you try to wrap this up before the sprint ends tomorrow?

          thanks,
          Jerry

          Show
          Jerry Neal (Inactive) added a comment - Jeff, Can you try to wrap this up before the sprint ends tomorrow? thanks, Jerry
          Hide
          Tom Clark added a comment -

          Of the three suggestions above, I think #3 makes the most sense in this case. The icons are now rendered via fonts and css (no images), so we would need a 'disabled' class to be applied to the icon, and from there we can create the appropriate disabled styling. The DOM output would looks something like this:

          <span class="icon-cool disabled"></span>

          Show
          Tom Clark added a comment - Of the three suggestions above, I think #3 makes the most sense in this case. The icons are now rendered via fonts and css (no images), so we would need a 'disabled' class to be applied to the icon, and from there we can create the appropriate disabled styling. The DOM output would looks something like this: <span class="icon-cool disabled"></span>
          Hide
          Claus Niesen added a comment - - edited

          User Experience Question:

          What should the disable behavior for the lookup, expand, data picker and spinner icons be?

          • Leave icons as is but make them inoperable.
          • Remove the icons. (Is there a danger of the layout changing?)
          • Replace them with inactive icons.

          Implementation question:

          How should we implement the disable features for the various widgets/controls that update an input field?

          • We can't just assume every widget needs to be disabled.
          • Adding new widgets should not require core KRAD code to be updated.
          Show
          Claus Niesen added a comment - - edited User Experience Question: What should the disable behavior for the lookup, expand, data picker and spinner icons be? Leave icons as is but make them inoperable. Remove the icons. (Is there a danger of the layout changing?) Replace them with inactive icons. Implementation question: How should we implement the disable features for the various widgets/controls that update an input field? We can't just assume every widget needs to be disabled. Adding new widgets should not require core KRAD code to be updated.

            People

            • Assignee:
              Jeff Covey (Inactive)
              Reporter:
              Tony Potts (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 4 hours
                4h
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 4 hours
                4h

                  Agile

                    Structure Helper Panel