Can't click on menu entries in Chrome with multiple: false

[bg]

With multiple: false set, I can't click on menu entries with Chrome. With the default multiple: true I don't have this problem. Other browsers seem to work fine. The only way I can make selections is to use arrow keys and press enter, but this doesn't work in conjunction with multiselectfilter.

Versions:

• Multiselect 1.12
• jQuery 1.7.1
• jQueryUI 1.8.17
• Chrome 16, Debian sid/unstable
• Chrome 17, Windows XP

[bg]

Something similar was reported to me by an IE9 user. Maybe HTML5 related, then? Oh well, switched to fnagel's selectmenu and I'm much happier with that than multiple=false for this widget.

[Ariesto]

Chrome 17.0.963.56 m, Windows 7

I was unable to replicate this issue. It worked fine for me....

http://www.erichynds.com/examples/jquery-ui-multiselect-widget/demos/single.htm

[bg]

Hmm. The other potential wrinkle is my own tests are over VNC to my Windows XP VM running in Virtualbox and VNC to my Debian/sid desktop. However, that doesn't explain the report from the IE9 user, so I think VNC isn't a part of the problem. It is more likely some conflict between your widget and other elements on the same page.

It's unlikely I'll get back to trying to narrow it down soon, since we're happy using fnagel's selectmenu instead. So, if you want to just consider this a local issue with my own code and close it, I would not be terribly offended. :)

Thanks, Ben

[kinwind]

I have the same problem. But, a little different. When I create a "multiple: false" with no selected item . It can click menu in ie9. When I create with selected item (default selected value). I can't click menu in ie9.

[panteracanes]

I was finding a similar issue in ie9 after post back within an ajax-ed area when the multiselect was in that area. What I found was that after postback, when clicking on the label (span) of single or multiselect was not working while clicking on the actual checkbox of multi was working. Also keyboard clicks were fine in both. When debuging the code I found that when mouse clicking on the label (span) in the drop down the event fired back and the self/this items had the namespace of the original binding while the checkbox (and I assume keyboard presses) had the latest namespace of the binding to the control. This was happening in the .delegate('input[type="checkbox"], input[type="radio"]', 'click.multiselect', function (e).

So I would get namespace .multiselect1 for the span event click while I would get something like .multiselect5 for the checkbox click event.

I figured out a work around, but not sure if it is the right or perfect one. Just know that it now works for ie7, ie8, and ie9 document modes for me in my case.

In the refresh function init, after the line: var id = el.attr('id') || multiselectID++; // unique ID for the label & option tags I added the following statement: if (id == el.attr('id')) { id = id + '_' + multiselectID; }

So when the elements would get rebound upon a page refresh they had different names/attributes than previous ones. It feels like a hack and that I don't fully understand what was happening but it works. I am posting this so maybe it helps the rest of you with this issue and maybe someone can come up with something that is more correct if there is a better way.

[mlh758]

I'm going to close this since it only seems to apply to older browsers we are no longer supporting.