MultiSelect's OptionsMenu Does Not Fire a CloseEvent Consistently Upon Closing

[Ri-gers]

MultiSelect<String> testSelect = MultiSelect.<String>create();
testSelect.getOptionsMenu().setAutoCloseOnSelect(false).setCloseOnBlur(true)
                .addCloseListener(component ->  GWT.log("CLOSED"));
for (int i = 0; i < 100; i++)
{
     testSelect.appendChild(SelectOption.create("Entry " + i));
}

The CloseEvent is not fired consistently in the above code. It seems to only happen if there are 'a lot' of options appended to the component. So, de/selecting items and clicking outside of the OptionsMenu does not always result in a CloseEvent fired. This seems to get worse the more items are in the menu

[vegegoku]

I still cant reproduce this one, the close listener is being triggered consistently for me. Any more hints on how to reproduce this?

[Ri-gers]

I still cant reproduce this one, the close listener is being triggered consistently for me. Any more hints on how to reproduce this?

Hmm, for me it happens with a low number of items and gets very consistent when e.g. using 1000 items (in general: the more items, the more consistently this happens). I simply open the dropdown, select an item and click outside of the dropdown to close it, then repeat this. This results in "CLOSED" not being printed to the log everytime (in my case, once the user would select some values, a call to the server would be triggered using the selected values which then in turn update some other fields in a form. Since this is often some expensive call, I only do it once the close event is fired. ChangeEvent works consistenly by the way, but I cannot use that because of the expensive calculation, that's the reason I rely on CloseEvents to collect the final user selection).

Can you reproduce it using more items (500, 1000, etc.)? Then it should happen very consistently. Two more notes: I'm mainly closing the dropdown by clicking outside of it, not using ESC and not clicking on the MultiSelect component. I'm using Chrome, so I'm not sure if your findings from #1017 might have an influence here. Also keep in mind that I'm using the last release build 2.0.3. Maybe some fixes you implemented for 2.0.4 (like #976) make this obsolete. If you cannot reproduce it, can you release 2.0.4 so that I can check again with all the changes?

[Ri-gers]

@vegegoku Could you reproduce it with my hints?

[vegegoku]

I actually tested with 3000 items. Can you test with SNAPSHOTS?

[vegegoku]

This is with 1500 select options and I still cant reproduce, I will close the issue assuming it was fixed automatically from a different fix.

Screencast.from.2025-03-19.13-40-53.webm

[Ri-gers]

Seems to fire consistently now, thanks