[KULRICE-7364] "disabled" property improvements Created: 22/May/12  Updated: 03/Apr/13  Resolved: 17/Oct/12

Status: Closed
Project: Kuali Rice Development
Component/s: Development
Affects Version/s: None
Fix Version/s: 2.2.0-m4, 2.2
Security Level: Public (Public: Anyone can view)

Type: Improvement Priority: Major
Reporter: Bob Hurt (Inactive) Assignee: Unassigned
Resolution: Complete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Similar issues:
KULRICE-7211Default datePicker widget disabled property to disabled property on control
KULRICE-13121Setting the disabled property on a ConcreteKeyValue in a KeyValuesFinder class does not disable that option in a drop down control
KULRICE-8126Collection control does not honor disable if disable is disabled by an expression for collection refresh
KULRICE-12721Improvements to property binding security
KULRICE-7976Allow table header to be disabled
KULRICE-7484Ajax Improvements- Add a preSubmitCall property to ActionField
KULRICE-12556disabledWhenChangedPropertyNames does not work with multiple property names configured
KULRICE-9846defaultValue not applied before disabled expression evaluation on initialization
KULRICE-5331UIF Framework - Add support for disabled on input controls
KULRICE-10395Allow for disabled expressions to be partially evaluated server side
Rice Module:
KAI Review Status: Not Required
KTI Review Status: Not Required


When a field becomes disabled, its validation should be set to valid. This would probably also effect prerequisite constraints, so a disabled field's dependencies would not be validated.

A second thing that would be very nice is if disabling/enabling could happen through javascript. This would make the UI much cleaner.

Comment by Jessica Coltrin (Inactive) [ 16/Oct/12 ]

moving non-blocker and non-critical m4 Jiras to 2.2-backlog

Generated at Sat Jul 04 04:17:19 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.