[KULRICE-9672] Progressive disclosure not working Created: 03/Jun/13  Updated: 12/Aug/13  Resolved: 17/Jun/13

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

Type: Bug Fix Priority: Blocker
Reporter: Jerry Neal (Inactive) Assignee: Jerry Neal (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Similar issues:
KULRICE-7996Progressive disclosure and refresh within table not working
KULRICE-7754Progressive disclosure via ajax not working in Kitchen Sink
KULRICE-8938problem with dropbox progressive disclosure in a lightbox
KULRICE-10633Multiple problems with KRAD Kitchen Sink Progressive Disclosure
KULRICE-11902Library - Client Responsiveness - Progressive Disclosure - Ajax Retrieval does not work - Field does not show up
KULRICE-11158Progressive disclosure and label condition doesn’t work for lookup view
KULRICE-8455Message for progressive disclosure appearing as 'null'
KULRICE-6340ajax progressive disclosure / refresh are broken
KULRICE-7550Fix progressive disclosure highlight animation styling
KULRICE-6568Progressive Disclosure server side improvements
Rice Module:
KRAD Feature Area:
UIF Component
KAI Review Status: Not Required
KTI Review Status: Not Required
Code Review Status: Not Required
Include in Release Notes?:


Progressive disclosure is not currently working. No errors are seen, the content just doesn't display. Maybe an issue related to JS refactoring?

Comment by Brian Smith (Inactive) [ 03/Jun/13 ]

This is not related to the js. The fix was to force the expression evaluator to use the correct model in apply model of component base, why this no longer contains the correct model is another question entirely and feels like a bug, can you let me know if you think you might know the answer to this? For now this particular bug is fixed though.

Comment by Jerry Neal (Inactive) [ 07/Jun/13 ]

Ah yes, this is due to the expression evaluator rework. Actually we should probably initialize the model in the run component lifecycle method. I'll make the adjustment. Thanks for looking into this

Generated at Sat Jul 11 15:07:47 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.