Signature help does not always correctly highlight the current argument when using keyword arguments

[FerretDetective]

Make sure you have done the following

• Updated to the latest version of blink.cmp
• Searched for existing issues and documentation (try <C-k> on https://cmp.saghen.dev)

Bug Description

When using keyword arguments in a language like python the order in which they are specified does not matter. When using blink, inputting keyword arguments that are out of order from the definition causes the wrong argument to be highlighted as the current.

Neovim with blink.cmp:

VSCode:

Relevant configuration

signature = { enabled = true }

neovim version

NVIM v0.10.3 Build type: RelWithDebInfo LuaJIT 2.1.1731601260 Run "nvim -V1 -v" for more info

blink.cmp version

v0.11.0

[Saghen]

Are you using the same LSP on both?

[FerretDetective]

Yes, I was using basedpyright for both.

I just tested it again, and it seems to behaving differently. When I reported this it seemed to occur whether or not I accepted the completion for the keyword argument (sep), but now it seems wrong only when I don't accept the completion.

The first one I don't accept the completion, and the second one I do:

Screencast_20250126_094704.webm