#33360 closed defect (bug) (fixed)
Weird Accordion Jump Glitch in Menu Customizer
Reported by: | mrahmadawais | Owned by: | westonruter |
---|---|---|---|
Milestone: | 4.4 | Priority: | normal |
Severity: | normal | Version: | 4.3 |
Component: | Customize | Keywords: | has-patch |
Focuses: | ui | Cc: |
Description
Tonight while testing the new Menu Customizer I found out that when an accordion is open and you click open another one, it jumps in a weird fashion, which seems like a glitch.
If you look at the speed at which an accordion opens up and the speed at which the last accordion moves up or down, you'll notice a big difference, and that's where the glitch is.
Attachments (2)
Change History (20)
This ticket was mentioned in Slack in #core by mrahmadawais. View the logs.
9 years ago
#2
follow-up:
↓ 3
@
9 years ago
- Component changed from Menus to Customize
- Focuses javascript removed
- Keywords needs-patch added
- Milestone changed from Awaiting Review to 4.3.1
#3
in reply to:
↑ 2
@
9 years ago
Replying to helen:
Thanks for the screencast mrahmadawais, very helpful. This is really janky feeling - let's see if we can smooth it out for 4.3.1.
Looking forward!
#4
@
9 years ago
See 33360.patch.
This one removes the min-height: 120px;
, which was causing the issue. Additionally, the patch adds a transition to the accordion title - this adds some eye-candy when expanding/collapsing (the transition time equals the expand/collapse animation time).
Can anyone recall why the min-height
is there in the first place?
#6
follow-ups:
↓ 7
↓ 8
@
9 years ago
I believe the height-setting that is done in JS supersedes the need for that min-height.
Can we get an after screencast for comparison?
#7
in reply to:
↑ 6
@
9 years ago
Replying to celloexpressions:
I believe the height-setting that is done in JS supersedes the need for that min-height.
Can we get an after screencast for comparison?
Just added one. Looks fine, but the closing behavior of content area can be slowed down a little. Maybe by introducing a .closing class with opening one?
#8
in reply to:
↑ 6
@
9 years ago
Replying to celloexpressions:
I believe the height-setting that is done in JS supersedes the need for that min-height.
I think on small screens (and in landscape orientation) there's the danger letting JS handle the height will set a very small height on the scrolling div, maybe min-height was there to always have an acceptable minimum height?
#9
@
9 years ago
- Milestone changed from 4.3.1 to 4.3.2
Sadly, we don't have a patch here yet. If someone wants to work up a patch we can still consider it for 4.3.1. In the mean time, however, I'm punting this to 4.3.2.
#10
@
9 years ago
Actually, there is a patch: 33360.patch, which works decent on all devices I've tested it on. Is there anything else that should be addressed here?
#11
follow-up:
↓ 12
@
9 years ago
It seems there is outstanding feedback from @mrahmadawais and @afercia that have not yet been addressed in the patch. Or is everyone satisfied with the patch?
#12
in reply to:
↑ 11
@
9 years ago
Replying to westonruter:
It seems there is outstanding feedback from @mrahmadawais and @afercia that have not yet been addressed in the patch. Or is everyone satisfied with the patch?
Thanks @westonruter. I tested the patch, seems to be working fine at my end.
Thanks for the screencast mrahmadawais, very helpful. This is really janky feeling - let's see if we can smooth it out for 4.3.1.