Skip to main content

Bug Tracker

Side navigation

#11457 closed bug (fixed)

Opened March 08, 2012 10:53PM UTC

Closed October 22, 2012 04:58PM UTC

Another slideToggle jump effect

Reported by: anonymous Owned by: gnarf
Priority: low Milestone: 1.8
Component: css Version: 1.7.1
Keywords: Cc:
Blocked by: Blocking:

A div contains a UL with LIs floated left and with percentage widths.

When slideToggle shows the div, sometimes there's a jump at the end of the animation.

This jsfiddle has 12 examples demonstrating the effect.

Giving the UL a width removes the jump, possibly making this a duplicate of #8370 and #9513. And the behavior is similar to #10662.

But it appears if the LI widths add up to 100%, the animation is smooth, which can be seen in the first and second examples.

And when the LI widths don't add up to 100%, there's a jump at the end of the animation.

And confounding things further, in the 10th example, the LI widths do add up to 100% yet there's a jump at the end of the animation.

This inconsistency in behavior may indicate a bug.

Attachments (0)
Change History (14)

Changed April 23, 2012 04:42PM UTC by rwaldron comment:1

component: unfiledcss
milestone: None1.8
owner: → gnarf
priority: undecidedlow
status: newassigned

@gnarf can you take a look at this?

Changed June 02, 2012 07:52PM UTC by mikesherov comment:2

resolution: → worksforme
status: assignedclosed

This is working on edge:

All hail the great, mysterious effects rewrite!

Changed June 03, 2012 01:40PM UTC by scottgonzalez comment:3

If it only works in edge shouldn't that be fixed and not worksforme?

Changed June 03, 2012 02:15PM UTC by mikesherov comment:4

resolution: worksforme
status: closedreopened

I suppose. I had seen a few times where we close as WFM when we don't know what fixed it, just that it now works. I can change to just fixed.

Changed June 03, 2012 02:15PM UTC by mikesherov comment:5

resolution: → fixed
status: reopenedclosed

Changed June 05, 2012 07:14PM UTC by gnarf comment:6

I'd like to try to figure out what was broken at least and write a unit for the fact that we fixed it....

Changed June 05, 2012 07:52PM UTC by mikesherov comment:7

feel free to reopen and write a test. I was just trying to triage open tixx. I seem to have failed :-\\

Changed June 05, 2012 10:39PM UTC by gnarf comment:8

resolution: fixed
status: closedreopened

Nah - it definitely closed now, but I'm going to reopen because we don't have a unit covering it, and I want to make sure we can't regress on this one, whatever magic it was that fixed it...

Changed June 12, 2012 02:46AM UTC by dmethvin comment:9

status: reopenedopen

Changed June 18, 2012 04:34PM UTC by mikesherov comment:10

owner: gnarfmikesherov
status: openassigned

Changed August 10, 2012 05:48PM UTC by dmethvin comment:11

milestone: 1.8None

Changed October 15, 2012 04:33AM UTC by mikesherov comment:12

milestone: None1.8
owner: mikesherovgnarf37

gnarf, I haven't found a good way to test this. I'm inclined to just close as fixed. If you'd like to tackle it, please do, other resolve as fixed.

Changed October 15, 2012 04:34AM UTC by mikesherov comment:13

owner: gnarf37gnarf

Changed October 22, 2012 04:58PM UTC by gnarf comment:14

resolution: → fixed
status: assignedclosed