Case: the dropdown should be shouwn above input. PositionDropdown function then operates by showing dropdown below (and  ".select2-search input" has no margin, it gets the wrong dropdown size). Then in the same function calculates the top value, but doesnt take into account, that input will have the "margin-top: 4px". Thus dropdown is displayed 4px lower.

Then the window resizes, the dropdown position is already correct, but then calculations (outerHeight()) get the height including the ".select2-search input" margin of 4px and thus moves the dropdown up.

Fix #2282.
When a select box is empty (this appends in my case, I have a dynamic select box), the search box should not be shown.

Hide search box if select is empty

Spelling mistake for jsDelivr

Add padding to select2 container displayed above

This chrome workaround had the undesired side-effect of preventing anything in the select2 drop from being focused (affected single but not multi selects for some reason). Making the condition more specific to the actual problem being worked around solves this.

don't display a hidden input on destroy

fix vietnamese grammar mistakes

Fix performance issue with setVal on MultiSelect

If you call element.attr ('style') with Zepto and
there is NO inline style, you get back the
CSS2Properties object. In jQuery you would get
nothing.

To avoid calling split in an object instead of a
string we should check if we really have a string.

Signed-off-by: Leo Unglaub <[email protected]>

Fixing issue #2864

Update copyright year

Remove aria-activedescendant attribute after the dropdown is closed,
to make sure the aria properties is vaild for aduit-tool
[https://code.google.com/p/accessibility-developer-tools/wiki/AuditRules#AX_ARIA_04:_ARIA_state_and_property_values_must_be_valid]

Fix accessible aria activedescendant attribute

Little typo

Ember JS component link.

The documentation for the current version is still at http://select2.github.io/select2/.

Once 4.0 moves on a little further, we will switch these links to https://select2.github.io/.

Update README.md

the dot, denoting a namespace and not an event name, was missing

Properly off() the events in the "select2" namespace

Fix bug where elements in select2 drop cannot be focused

This fixes #2942.

The `debug` option was chosen because the option also exists in
Select2 4.0.0 and provides similar warnings when configurations
are detected that are known to cause issues in Select2.

Warnings will be displayed in the console if the debug option is
enabled. As there are a lot of options that have been renamed in
Select2 4.0.0, using the older version of the options will trigger
a warning in Select2 3.5.3. Options which were also removed and
have clear migration paths will also trigger a warning with the
link to the relevant documentation.

Options which have been renamed in Select2 4.0.0 are now supported
in Select2 3.5.3, allowing people to migrate their installations
over to the new options before making the final switch.

This closes #3483.

Definitely a syntax error perhaps != was the intention?

!- maybe means != ?

The local variable defined will overwrite the tags function, since the var will get hoisted to the functional scope

Fix broken tags, #3695

This issue only affected single selects and should have happened when
calling `select2('data')` when passing in the new data object to select.

This closes #3694

Add missing png in jspm files declaration on 3.5.2