Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: 3.3
-
Fix Version/s: EE-3.3.0.GA, 4.0.BETA, 4.0
-
Component/s: ACE-Components, Framework
-
Labels:None
-
Environment:ACE
-
Assignee Priority:P1
Description
With ICE-8922 and the new server-side determination of updated elements, there is a key difference in implementation. Before, a component could register multiple onElementUpdate callbacks on a single element id, but now there can be only one. DateTimeEntry has a problem with this, since it current registers two different callbacks on its root element.
Either we will need to augment the registration code to support a chaining of multiple registrations, to maintain there being a single callback, or we'll need this component to be refactored to only use one callback.
Either we will need to augment the registration code to support a chaining of multiple registrations, to maintain there being a single callback, or we'll need this component to be refactored to only use one callback.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
| Field | Original Value | New Value |
|---|---|---|
| Assignee | yip.ng [ yip.ng ] | |
| Fix Version/s | 3.4 [ 10770 ] |
| Fix Version/s | EE-3.3.0.GA [ 10572 ] |
| Assignee Priority | P1 [ 10010 ] |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Duplicate [ 3 ] |
| Issue Type | Improvement [ 4 ] | Bug [ 1 ] |
| Fix Version/s | 4.0 [ 11382 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |