Details
-
Type: Improvement
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 3.2
-
Fix Version/s: EE-3.3.0.GA, 4.0.BETA, 4.0
-
Component/s: ACE-Components
-
Labels:None
-
Environment:All
-
Assignee Priority:P3
-
Salesforce Case Reference:
-
Affects:Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial
Description
Feature Request: Add the ability to disable all input fields located in an ace:panel without individually changing each component. This functionality would be different than disabling the functionality of the ace:panel itself (expand/contract).
Committed new feature to the trunk at revision 33754.
Testing notes:
1. Create a new test page with an ace:panel containing some input components.
2. Add the new 'disableInputs' attribute to the ace:panel and bind its value to a boolean property. Also bind the same property to a checkbox outside the panel.
3. Add an h:commandButton outside the panel to submit the whole form.
4. Verify that when this option is activated, when submitting the form, the values of these input components aren't sent to the server in the request body. Also verify that when this option is deactivated, the values of these input components are sent to the server.
Note: This option only affects the components in the client. It doesn't change their internal state. Thus, some components might not look disabled, as when using their own disabled attribute, because their renderers won't be aware that these components are disabled and won't apply all the extra styling and markup when they are disabled. However, their input elements in the client should be disabled and their values not included in the request body.