[KULRICE-12441] Library - Controls - Disable on Key Event examples are ambiguous Created: 09/Apr/14  Updated: 21/Apr/14  Resolved: 11/Apr/14

Status: Closed
Project: Kuali Rice Development
Component/s: Development
Affects Version/s: 2.4
Fix Version/s: 2.4
Security Level: Public (Public: Anyone can view)

Type: Bug Fix Priority: Major
Reporter: Jeff Ruch Assignee: Kristina Taylor (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0 minutes
Time Spent: 1 hour
Original Estimate: 1 hour


Issue Links:
cloned to KULRICE-12442 Library - Containers - Groups - Secti... Closed
discovered by KULRICE-13753 2.4.0 Coordinated Developer Testing (... Closed
Rice Module:
Application Requirement:
Sprint: 2.4.0-rc1 Sprint 8
KAI Review Status: Not Required
KTI Review Status: Not Required
Code Review Status: Not Required
Include in Release Notes?:


Library - Controls - Disable on Key Event examples are ambiguous.

Many of the controls have a 'Disable on Key Event' example. The title should be enable on key event as the example starts off as disabled and then becomes enable on a key event. The controls with this include Radio Control, Text Control, Text Area Control, Password Control.

Comment by Kristina Taylor (Inactive) [ 11/Apr/14 ]

Actually, the problem here is that the examples (including Checkbox which uses it slightly differently) are demonstrating the evaluateDisabledOnKeyUp property, so the name should probably be "Evaluate Disabled on Key Up". That way it keeps the consistency of demonstrating properties. I think adding "Evaluate" should help since it notes that it is evaluating whether it should be disabled on every key up. I will also make Checkbox work consistently with this.

Generated at Mon Jan 18 20:48:08 CST 2021 using JIRA 7.0.11#70121-sha1:19d24976997c1d95f06f3e327e087be0b71f28d4.