Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid error on empty search result in MultiSelect. Fixes #2942 #2943

Closed
wants to merge 28 commits into from

Conversation

vinntreus
Copy link

No description provided.

stonys and others added 28 commits October 29, 2014 15:45
Added padding to ".select2-search" container instead of margin for ".select2-search input". This fixes bug of "#select2" movement when resizing page.

Steps to reproduce the bug:
- open select2 so it appears above the input
- resize the window

Actual results:
- #select2-drop moves up by 4px

Expected results:
- #select2-drop stays in same place
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 select2#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
…input

don't display a hidden input on destroy
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 <leo@leo-unglaub.net>
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
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/.
the dot, denoting a namespace and not an event name, was missing
Properly off() the events in the "select2" namespace
@kevin-brown
Copy link
Member

Now that 4.0.0 has been released, the branches have switched and this is pointing to the wrong one. If you are still interested in getting this merged, create a new pull request for the stable/3.5 branch and link back to this old one.

Until then, we have to close this off as it is not possible to merge it in.

@kevin-brown kevin-brown closed this May 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

10 participants