Search and Top Navigation
#9395 closed bug (wontfix)
Opened June 24, 2013 11:49AM UTC
Closed June 24, 2013 12:29PM UTC
Last modified June 24, 2013 12:37PM UTC
ACCORDION IGNORES FIRST ITEM AFTER BEING CLONED
Reported by: | simon.ferndriger | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | none |
Component: | ui.accordion | Version: | 1.10.3 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
When cloning an element containing an accordtion with events, the accordion missbehaves. No matter which state the accordion was in before, the new cloned accordion opens the first item automatically. And when clicking on other items, the first item stays open! It is, as the accordion forgot about the first item at all. Only after collapsing the first item, the accordion then works just as expected.
Have a look at the
Steps to reproduce failure
Click on section 2 -> section 1 stays open
Click on section 1 -> the accordion works (now)
Have a look at the
Attachments (0)
Change History (3)
Changed June 24, 2013 11:54AM UTC by comment:1
_comment0: | == Steps to reproduce failure == \ \ 1. Click on section 2 -> section 1 stays open \ 2. Click on section 1 -> the accordion works (now) → 1372074923015387 |
---|---|
_comment1: | == Steps to reproduce failure == \ \ 1. Click on section 2 -> section 1 stays open (instead of closing -> bug!) \ 2. Click on section 1 -> from now on, the accordion works → 1372075023427213 |
Changed June 24, 2013 12:29PM UTC by comment:2
resolution: | → wontfix |
---|---|
status: | new → closed |
Hi simon.ferndriger,
Thanks for taking the time to contribute to the jQuery UI project. Unfortunately, cloning widgets is not supported: http://contribute.jquery.org/wont-fix/.
Changed June 24, 2013 12:37PM UTC by comment:3
Ah, OK.
Steps to reproduce failure
1. Click on section 2 -> section 1 stays open (instead of closing -> bug!)
2. Click on section 1 -> from now on, the accordion works
Additional issue
When hiding ALL items by default with "active: false", the cloned accordion will still show the first element by default (which it shouldn't, strictly speaking! -> bug!)