Uploaded image for project: 'Kuali Rice Development'
  1. Kuali Rice Development
  2. KULRICE-10883

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

          Details

          • 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

              Attachments

                Issue Links

                is duplicated by

                Bug Fix - A problem which impairs or prevents the functions of the product. KULRICE-7141 Verify that Disabled for datepicker and lookup widgets can be disabled client-side when disabled on the fly

                • Major - Major loss of function.
                • Closed
                is related to

                Task - A task that needs to be done. KULRICE-7211 Default datePicker widget disabled property to disabled property on control

                • Major - Major loss of function.
                • Closed
                relates to

                Bug Fix - A problem which impairs or prevents the functions of the product. KULRICE-12616 Date Picker icon still has color even when disabled

                • Major - Major loss of function.
                • Open

                Bug Fix - A problem which impairs or prevents the functions of the product. KULRICE-12615 Text Area still editable even when disabled

                • Critical - Crashes, loss of data, severe memory leak.
                • Closed

                Task - A task that needs to be done. KULRICE-13688 Fill AFT per-screen item gap: KRAD Library: Client Reponsiveness: Disable

                • Major - Major loss of function.
                • Closed

                  Activity

                  Ascending order - Click to sort in descending order
                  Hide
                  Permalink
                  cniesen 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
                  cniesen 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.
                  Hide
                  Permalink
                  thrclark 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
                  thrclark 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
                  Permalink
                  jkneal Jerry Neal (Inactive) added a comment -

                  Jeff,

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

                  thanks,
                  Jerry

                  Show
                  jkneal Jerry Neal (Inactive) added a comment - Jeff, Can you try to wrap this up before the sprint ends tomorrow? thanks, Jerry
                  Hide
                  Permalink
                  acampbell Adam Campbell (Inactive) added a comment -

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

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

                    People

                    • Assignee:
                      jcovey Jeff Covey (Inactive)
                      Reporter:
                      apotts 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