Tab autocomplete jumps back to an earlier method call

When autocomplete is used for more than one method call in an expression, pressing Tab can move the cursor back into an earlier call instead of accepting the current suggestion. For example, after completing App.MajorVersion.ToString() and continuing to App.MinorVersion.ToS, Tab can jump into the first ToString() and leave the second call incomplete.

Expected behaviour: after the cursor leaves an earlier call, Tab should accept the suggestion at the current cursor position. Tab should continue to cycle through parameter placeholders while the cursor is editing those parameters.