Details
-
Type: Improvement
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 3.0.RC1
-
Fix Version/s: 3.1.0.BETA1, 3.1
-
Component/s: ACE-Components
-
Labels:None
-
Environment:IF 3.0
Description
Having ClientBehaviours generate request input rather than complete functions would allow us much greater component-level control of the ClientBehaviours defined by the client.
Issue Links
- blocks
-
ICE-7652 ace:dataTable: ace:ajax event "editSubmit" causes the row to remain editable until clicking cancel
- Closed
-
ICE-7672 Showcase: ACE:DataTable multiple cell selection with ajax demo not functioning correctly
- Closed
-
ICE-7681 ace:accordion with panechange event used with ace:ajax - not receiving events if dynamic attribute is enabled
- Closed
We should find a way so that when the ace:ajax tag is absent, the @ClientBehaviour's defaultRender and defaultExecute are used, or evaluate if we want two defaults: a tag present default and a tag absent default. That would be analogous to tag-absent being equivalent to singleSubmit=false and tag-present being equivalent to singleSubmit=true, with the present defaults determining what is being executed and rendered ala ice.se/ice.ser.