[KULRICE-12301] View flag for disabling growls should disable client side growls as well Created: 27/Mar/14 Updated: 16/Jan/15
|Project:||Kuali Rice Development|
|Component/s:||Development, User Experience (UX)|
|Security Level:||Public (Public: Anyone can view)|
|Reporter:||Jerry Neal (Inactive)||Assignee:||Unassigned|
|Remaining Estimate:||1 day|
|Time Spent:||Not Specified|
|Original Estimate:||1 day|
|Epic Link:||Technical Issues|
|KAI Review Status:||Not Required|
|KTI Review Status:||Not Required|
|Code Review Status:||Not Required|
|Include in Release Notes?:||
The view component has property growlMessagingEnabled. This was originally added when adding the Growl type to MessageMap. The intention was if growls were added to the mesage map, to allow them to be displayed as info messages instead.
However, growls are also shown client side in places (like the validation framework), and there is no way to prevent them without overriding code. It makes sense for this view property to disable all growls for a view regardless of where they come from. Therefore we need to modify the client side code to check this view setting.
Note the related Jira on validation handling. It might be decided that growls should not be used at all for validations, therefore this would become irrelevant.
Finally, the javadocs isGrowlMessagingEnabled and setGrowlMessagingEnabled have some content and formatting issues that need cleaned up.
|Comment by Jerry Neal (Inactive) [ 28/Apr/14 ]|
Another possibility. We now only use growls to display JS error notifications. However, we are considering how those notifications are given.