#3952 closed bug (notabug)
Show / SlideDirection
Reported by: | Nikola | Owned by: | Nikola |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | ui.effects.core | Version: | 1.6rc5 |
Keywords: | show, slide | Cc: | |
Blocked by: | Blocking: |
Description (last modified by )
I've found some problems using show and slideUp / slideDown functions specifically with drop down menus. I've included a minimal test case which demonstrates everything and is commented.
Change History (16)
comment:1 Changed 14 years ago by
comment:2 Changed 14 years ago by
Milestone: | TBD → 1.6 |
---|---|
Priority: | major → critical |
comment:5 Changed 14 years ago by
I'm not sure what happened to my paste at JS Bin. I pasted it again now but the JS bin isn't being very cooperative tonight. http://jsbin.com/itegi/edit.
comment:6 Changed 14 years ago by
Milestone: | 1.7 → 1.8 |
---|
comment:8 Changed 14 years ago by
We'll get back to this for alpha2, when merging dev/effects to trunk.
comment:9 Changed 14 years ago by
Description: | modified (diff) |
---|
comment:10 Changed 13 years ago by
Milestone: | 1.8 → 1.next |
---|
comment:11 Changed 12 years ago by
Priority: | critical → major |
---|
comment:12 Changed 12 years ago by
Playing around with jörn's demo I'm not seeing any problems -- Can we get a fiddled example?
comment:13 Changed 12 years ago by
Milestone: | 1.next → TBD |
---|
comment:14 Changed 12 years ago by
Owner: | set to Nikola |
---|---|
Status: | new → pending |
comment:15 Changed 12 years ago by
Resolution: | → invalid |
---|---|
Status: | pending → closed |
Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!
I've noticed this problem is still happening in rc6. Any updates on this or perhaps something I can do to avoid the problem?