Easyadminbundle: Autocomplete widget does not close since 2.1.2

[jdeveloper]

I updated Easyadmin from 2.1.1 to 2.1.2 and the autocomplete widget stops working as expected. I click, start typing, options appear, I click an option but the widget does not disapear.

[javiereguiluz]

I can't reproduce :( Using 2.1.3-DEV, which is the same as 2.1.2, in a real app, the autocomplete widget works as expected (I changed the font family to hide the app details):

[WebDaMa]

Same issue here, focus stays on autocomplete.
Can't even click another form field anymore.

[Kraddle]

For me too v2.1.2 with symphony 4.2.8
Maybe select2 bug ?
https://github.com/select2/select2/issues/5499

[gonzaloalonsod]

Yes select2 bug in version 4.0.6

[jakagacic]

Same here

[ktrzos]

This PR should fix it on EasyAdmin side: #2720.

[TracKer]

Just tried #2720, working perfectly.

For those who need this solution quickly up and running, just use "cweagans/composer-patches" package and add this to "extras" in "composer.json":

"patches": {
  "easycorp/easyadmin-bundle": {
    "Downgrade of select2 to 4.0.5 #2720": "https://patch-diff.githubusercontent.com/raw/EasyCorp/EasyAdminBundle/pull/2720.patch"
  }
}

[niko06300]

Just tried #2720, working perfectly.

For those who need this solution quickly up and running, just use "cweagans/composer-patches" package and add this to "extras" in "composer.json":

"patches": {
  "easycorp/easyadmin-bundle": {
    "Downgrade of select2 to 4.0.5 #2720": "https://patch-diff.githubusercontent.com/raw/EasyCorp/EasyAdminBundle/pull/2720.patch"
  }
}

I have an error with it : "Could not apply patch! Skipping. The error was: Cannot apply patch https://patch-diff.githubusercontent.com/raw/EasyCorp/EasyAdminBundle/pull/2720.patch" do you have any idea ? Thanks

[javiereguiluz]

@niko06300 no need to do that. The fix has been merged in master. I'll release a new stable version soon. Meanwhile you can use either EasyAdmin 2.1.1 or dev-master. Thanks.

[Gemorroj]

@javiereguiluz see https://github.com/select2/select2/releases/tag/4.0.7

[pierrebrzezny]

The bug persists in version 2.2