Autocomplete extension changes precedence of all keymaps

It seems that the autocomplete extension changes the precedence of all keymaps to highest. Is this intentional? I’m guessing not, as it seems quite odd.

Here’s an example. It registers a keydown handler via a plugin and another via a custom keymap. Without the autocomplete extension, a keydown event is handled first by the plugin, then the keymap, as expected:

Adding the autocomplete extension reverses that:

Specifying the plugin with the highest precedence (high does not work) fixes it:

That is indeed weird. This patch should help.

1 Like

So fast. Thanks!