The cursorWordPart* commands are limited to editor text, unlike the other cursorWord* commands

[travisclagrone]

• VSCode Version: 1.36.0 (system setup)
• OS Version: Windows_NT x64 10.0.18362

Steps to Reproduce:

1. Focus on a non-editor input text field (e.g. execute the command workbench.action.quickOpen or actions.find, inter alia)
2. Insert the text of the multi-part word "fooBar".
3. Move the cursor to the end of the multi-part word text.
4. Enter your keybinding for the command cursorWordPartLeft.

Expected behavior:

• Cursor moves to between "foo" and "Bar", i.e. foo|Bar.

Actual behavior:

• No effect.

Notes:

• This limitation appears in all inputText contexts other than the editorText context.
• This limitation affects all the cursorWordPart* commands:
  • cursorWordPartLeft
  • cursorWordPartLeftSelect
  • cursorWordPartRight
  • cursorWordPartRightSelect
  • cursorWordPartStartLeft
  • cursorWordPartStartLeftSelect
• The corresponding whole-word commands (those without the "Part" infix) are not limited, i.e. they function in inputText contexts other than the editorText context.

Does this issue occur when all extensions are disabled?: Yes

[mattkrick]

worth noting this isn't just an issue with find. would love to see this in the F2 to rename input!

[gsmetal]

Please, this is one of the most hurting moment when switching from Atom 🙏

[JWess]

I encounter this many times per day when trying to use F2 to rename a variable. It's unfortunate that it's been dormant in the backlog since 2020 (when it did receive enough community upvotes to be moved to the backlog).

Here is what happens if I hit F2 to rename a function's parameter and then activate the deleteWordPartLeft command:

[JWess]

Related to #53666