IE Auto-Width Bouncing Scrollbar

[locux]

I noticed that when we adjust the CSS to allow the width to auto-size to the content in IE10+ the scroll bar (when clicked) will often jog to the left the width of the scrollbar. Feels glitchy. Only happens in IE10+. IE9 will cut-off the right side of the select options.

Here's a fiddle displaying the issue: http://jsfiddle.net/rdX5R/4/

This was fixed in 0.8.5 with the following diff. (lines might be very slightly off from 0.8.5 as my source diff has patch already committed from bug #182.

17c17
<

---
>         var widthcount = 0;
1545a1551,1557
>                     if (widthcount == 0) {
>                         self.$dropdown_content.css({
>                             width: self.$dropdown_content.width() + 15
>                         });
>
>                         widthcount = 1;
>                     }

Here's a fiddle with this patch: http://jsfiddle.net/rdX5R/5/

p.s. This fix also solved issue #173 for me.

[locux]

after-thought: my proposed patch puts the initial "var widthcount=0;" within the sifter.js code. Should be down in the selectize.js section (around line 603).

[jeacott]

this fix is just what I need, but it doesn't work for remote loaded content.

if instead I try this:

positionDropdown: function() {
            var $control = this.$control;
            var offset = this.settings.dropdownParent === 'body' ? $control.offset() : $control.position();
            offset.top += $control.outerHeight(true);

            this.$dropdown.css({
                width : $control.outerWidth()+60,
                top   : offset.top,
                left  : offset.left
            });
        },

I can kinda get what I'm after. without it my content is all clipped.
Unfortunately I'm trying to use selectize in a bootstrap style sidepanel (ie inside span4 of 12),
and the droplist part of the selectize control wont expand past the span4. I've tried fiddling with the css but I'm just about to give up :(

[joallard]

Thanks for reporting this issue. I am closing it since this issue has been inactive for more than 2 years. If there is still a problem with the latest version, please re-open and add details following the Issue reporting guide.