Hi,
It is an indended behavior for cases when the search results are not closed on blur events and the seleciton does not get covered up. It’s a bit problematic to get it right as both elements are fixed or absolute positioned, so one will hover over the other.
In your case if it fits better you can force it’s z position via this custom CSS:
.asp_select2-container {
z-index: 10 !important;
}This should place the selection container below the results container on the z axis.
It will however still hover over the search input, that is technically impossible to avoid. An absolute or fixed positioned element in a higher up relative descendant (the results and the floating selection in the body element) will always have precedence over elements lower down the DOM tree (the search box within the content).