With `showResultsWhileTyping: true`, selecting a dropdown result via mouse click behaves differently than selecting it via ENTER

[juliusv]

When setting showResultsWhileTyping: true, the geocoder behaves differently depending on whether I select a dropdown search result via a mouse click (correct behavior) vs. navigating down to a result with the arrow keys and then pressing ENTER (incorrect behavior).

• Mouse click: The map selects the clicked-on result, shows a marker for it (and optionally flies to it)
• ENTER: The map selects multiple of the currently shown dropdown results and shows markers for each of them.

In the ENTER case, it still also fires a result event with just the one selected result. Just that it also does the extra unintended behavior.

It seems like I can work around this behavior difference by setting showResultMarkers: false, in which case it just shows a marker for the single selected result.

[HarelM]

The codebase is fairly straight forward, feel free to just open a PR that solves this...

[JakobMiksch]

I was surprised by the behaviour as well. The workaround of @juliusv works for me as well:

const options = {
  maplibregl: mapInstance,
  showResultsWhileTyping: true, 
  showResultMarkers: false, 
};

const geoCoder = new MaplibreGeocoder(geocoderApi, options);