Opened 10 years ago

Closed 9 years ago

#9141 closed defect (fixed)

AccordionContainer: layout glitch during animation

Reported by: martinpeschke Owned by: bill
Priority: low Milestone: 1.6
Component: Dijit Version: 1.3.0
Keywords: AccordionContainer Cc:
Blocked By: Blocking:

Description

In the examples (http://docs.dojocampus.org/dijit/layout, e.g. last example), with at least 3 ContentPane? in the AC,

When the lowest Pane is minimized and any other is clicked & maximized, the bottom most ContentPane?-Title gets crunched/squeezed/pushed down, for the duration of the animation.

The final display does not show this Crunch/Squeeze?.

Change History (3)

comment:1 Changed 10 years ago by bill

Milestone: tbdfuture
Priority: highlow
Summary: dijit.layout.AccordionContainerAccordionContainer: layout glitch during animation

I see this on FF/mac, although it works OK on safari. Didn't try IE.

comment:2 Changed 9 years ago by bill

Milestone: future1.6
Owner: set to bill
Status: newassigned

comment:3 Changed 9 years ago by bill

Resolution: fixed
Status: assignedclosed

(In [22677]) Fix AccordionContainer rendering problems, by properly accounting for margin/border/padding and by dealing w/the fact that during the animation, on claro, need to account for two blue borders wrapping around the two "active" children. See comments in code for more details.

This fixes the problem where the animation doesn't work well when there's lots of padding on the child ContentPane, and also the problem where the blue trim underneath a child ContentPane (claro only) would disappear during the animation.

Also, added correct handling for race condition when another pane is selected or the accordion is destroyed while an animation is in progress.

IE6 and IE7 have overflow problems with this new design (the overflow: hidden isn't taking effect), but rather than fix the problem I just disabled the animation for those browsers.

Fixes #4017, #7389, #9141 !strict.

Also removed some workaround code for #11415, and from [21426] (#10527), that seems to no longer be needed.

Note: See TracTickets for help on using tickets.