Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 3.0.RC1
-
Component/s: ACE-Components
-
Labels:None
-
Environment:IF 3, ACE components
-
Assignee Priority:P1
-
Affects:Documentation (User Guide, Ref. Guide, etc.)
Description
The following components have their ace:ajax behaviour handling written such that it makes the non ace:ajax-style component request, followed by an extraneous request to trigger the ace:ajax execute/render and listener, when one would expect those render/execute targets to be the targets of the previous request and the ace:ajax listener to be activated during the same lifecycle as the previous request.
This behaviour was originally specced this way, but subsequent investigation has shown this to be incorrect. The expected behaviour is that the ace:ajax submit will take precedence in cases where the same event would trigger both an event listener attribute on the component and a defined event ace:ajax tag. This is consistent with standard f:ajax tag behaviour as well.
Thus, the following components need changes so that the defined ace:ajax behaviour submits the params that the component request normally does.
ace:accordion
ace:droppable
ace:progressBar
ace:resizable
ace:tooltip
This behaviour was originally specced this way, but subsequent investigation has shown this to be incorrect. The expected behaviour is that the ace:ajax submit will take precedence in cases where the same event would trigger both an event listener attribute on the component and a defined event ace:ajax tag. This is consistent with standard f:ajax tag behaviour as well.
Thus, the following components need changes so that the defined ace:ajax behaviour submits the params that the component request normally does.
ace:accordion
ace:droppable
ace:progressBar
ace:resizable
ace:tooltip
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion