I'm using the fantastic select2 component in my Wicket 6.7 application via the Wicket-select2 integration package [ https://github.com/ivaynberg/wicket-select2/], version 2.2.2.
It works great on a regular page. On a page, clicking outside of the select2 component causes the component to close. However, when used in a Wicket ModalWindow, clicking outside of the select2 component (i.e., clicking somewhere else in the ModalWindow) does not cause the component to close. Some issues have been reported around this ( https://github.com/ivaynberg/wicket-select2/issues/13, https://github.com/ivaynberg/wicket-select2/issues/35) and the tickets say the issue should be fixed in select 3.3.0. Version 2.2.2 of the wicket-select2 package includes version 3.3.2 of select2. However, I'm still seeing the problem. Is anyone else seeing this behavior? Should the issue be fixed? Thanks Andrew
