Signature help points one parameter behind

[T1mL3arn]

Sometimes when you type fast (fast means faster than vscode processes it) it feels like signature completion points one parameter behind.
Video to show the problem

one.parameter.behind.mp4

Looks like the next parameter is shown only when a non-empty char is typed. Could it be changed to highlight the next parameter just after the coma char?

[AlexHaxe]

current workaround: use "editor.autoClosingBrackets":"never"

[kLabz]

Just to add: this isn't 100% due to that settings (and other editors' equivalent), as it also reproduces when editing code inside parenthesis (as in hasArguments(|))

Repro both OK and NOK behaviors on nvim with auto closing off:

Not sure yet if Haxe LSP or Haxe compiler issue.