[KULRICE-10883] Date picker (and other widgets) still work when a field is disabled Created: 08/Oct/13  Updated: 24/Sep/14  Resolved: 11/Mar/14

Status: Closed
Project: Kuali Rice Development
Component/s: Development, User Experience (UX), User Interface
Affects Version/s: None
Fix Version/s: 2.5
Security Level: Public (Public: Anyone can view)

Type: Bug Fix Priority: Critical
Reporter: Tony Potts (Inactive) Assignee: Jeff Covey (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0 minutes
Time Spent: 4 hours
Original Estimate: 4 hours

Issue Links:
is duplicated by KULRICE-7141 Verify that Disabled for datepicker a... Closed
relates to KULRICE-12616 Date Picker icon still has color even... Open
relates to KULRICE-12615 Text Area still editable even when di... Closed
relates to KULRICE-13688 Fill AFT per-screen item gap: KRAD Li... Closed
is related to KULRICE-7211 Default datePicker widget disabled pr... Closed
Epic Link: Components
Rice Module:
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?:


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

Comment by Claus Niesen [ 27/Jan/14 ]

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.
Comment by Tom Clark [ 17/Feb/14 ]

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>

Comment by Jerry Neal (Inactive) [ 10/Mar/14 ]


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


Comment by Adam Campbell (Inactive) [ 05/May/14 ]

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

Generated at Tue Oct 20 20:17:53 CDT 2020 using JIRA 7.0.11#70121-sha1:19d24976997c1d95f06f3e327e087be0b71f28d4.