Details
-
Type: Improvement
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 2.0.2
-
Component/s: ACE-Components
-
Labels:None
-
Environment:ACE
-
Assignee Priority:P2
Description
With ICE-6728, we disabled animations for changing tabs with the tabSet component. As well, we're looking at revamping our animation support in general, so we've decided to defer the effort for re-enabling that feature.
Issue Links
Activity
Mark Collette
created issue -
Mark Collette
made changes -
Field | Original Value | New Value |
---|---|---|
Salesforce Case | [] |
Mark Collette
made changes -
Salesforce Case | [] | |
Fix Version/s | 2.1 [ 10241 ] | |
Assignee | Mark Collette [ mark.collette ] |
Mark Collette
made changes -
Ken Fyten
made changes -
Salesforce Case | [] | |
Assignee Priority | P2 | |
Assignee | Mark Collette [ mark.collette ] | Arturo Zambrano [ artzambrano ] |
Arturo Zambrano
made changes -
Ken Fyten
made changes -
Salesforce Case | [] | |
Fix Version/s | 2.1-Beta2 [ 10294 ] |
Arturo Zambrano
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
In the old code tabSet javascript code, we would hook into the tabSet's tab change listener's submit listener, to do some processing after the server had rendered the new tab content. So we'd have both the old tab and the new tab available for doing animations on. With the new code, it uses an ondomready call that defers the processing of the new tab contents until after the submit listener would have been invoked. This means that we don't have that simple place to access both tabs for animations. Possibly we'll need to do the animation for hiding the old tab, and then do the submit, and then do the animation for showing the new tab.