DropDown-Check-List does not work in Accordian

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create a basic accordian using the jquery UI library
2. Add a CheckBoxList inside of the content of one of the panels
3. Open the CheckBoxList

What is the expected output? What do you see instead?
Expect the dropdown menu to be positioned below the selector.
Unfortunately, it is positioned significantly away from where it should be.

What version of the product are you using? On what operating system?
Version: 0.8. Operating System: Windows 7 Browser: FireFox 3.5 

Original issue reported on code.google.com by a.parano...@gmail.com on 20 Dec 2009 at 2:59

[GoogleCodeExporter]

I've experience the same issue.  Any workarounds in the meanwhile until the 
next release?

Original comment by jflo...@gmail.com on 29 Dec 2009 at 12:06

[GoogleCodeExporter]

Can you please provide a sample html to reproduce the problem? I just checked 
it with 
something like:

<div id="accordion">
        <h3><a href="#">First header</a></h3>
        <div>First content
            <select id="s1" multiple="multiple">
                <option>Low</option>
                <option>Medium</option>
                <option>High</option>
            </select>
        </div>
        <h3><a href="#">Second header</a></h3>
        <div>Second content</div>
    </div> 

and js:

$("#accordion").accordion();
$("#s1").dropdownchecklist();

and all seems to work just fine.

Original comment by adrian.tosca on 9 Jan 2010 at 7:35

[GoogleCodeExporter]

Hello adrian.tosca,

Thank you for taking a look at this. I have provided an isolated code sample. I 
look
forward to learn what you find.

Original comment by a.parano...@gmail.com on 10 Jan 2010 at 3:13

Attachments:

• CheckBoxListTest.zip

[GoogleCodeExporter]

Thank you for your time, there was indeed a problem both with positioning (easy 
to 
fix) but also with the z-index (more complicated).

I ended by reverting to a previous version where the drop container is in the 
body 
instead of having the same parent as the visible control. Even if the later has 
the 
advantage of a normal tab index making it usable with the keyboard, has a lot 
of 
positioning side effects almost impossible to fix in all contexts. 

It should work ok now with the version in trunk.

Original comment by adrian.tosca on 10 Jan 2010 at 4:41

• Changed state: FixedInTrunk

[GoogleCodeExporter]

Awesome, thank you for this fix.

Original comment by jflo...@gmail.com on 12 Jan 2010 at 2:27

[GoogleCodeExporter]

Original comment by adrian.tosca on 16 Jan 2010 at 7:37

• Changed state: Fixed