Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Invalid
-
Affects Version/s: 3.2
-
Fix Version/s: 3.3
-
Component/s: ACE-Components
-
Labels:None
-
Environment:IF 3.2
-
Assignee Priority:P1
Description
The DataTable, since retiming these manipulations to occur after child update iteration in the UpdateModel phase of the lifecycle, can add events to be executed following.
I would prefer recasting existing event types as "pre-filter", "pre-sort", "pre-page", and record this as an API deviation in the new version.
I would prefer recasting existing event types as "pre-filter", "pre-sort", "pre-page", and record this as an API deviation in the new version.
Issue Links
- depends on
-
ICE-7751 ace:ajax merge multiple ClientBehaviours for the same event to execute during a single request
- Closed
Well I've discovered that this effort has been misguided.
The page, filter and sort listeners all became post-event after we moved the feature processing to updateModel (in ICE-8593). This means that listener behaviour changed in 3.2. Use of the immediate keyword currently allows pre-event listeners.
The ace:ajax listeners were always running at invoke application, which just happened to be pre-event due to the execution point of sort/filter/page.
However this work did at least uncover the missing portion of
ICE-7751that enables multiple ace:ajax tags for the same event type.