microsoft / microsoft/vscode-pull-request-github

Cannot move cursor in PR text area with ctrl+p and ctrl+f on mac OS

Open
#6,597 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

feature-request
Dominant language
TypeScript
Stars
2.6k
Forks
795
Avg merge
1d 4h
Merged PRs (30d)
46

Description

I want move cursor in PR text area with ctrl+p(cursorUp) and ctrl+f(cursorRight).
PR text area context is not textInputForcus.
I don't know why it is working ctrl+a, ctrl+e, ctrl+b.

Versions

GHPR Version: 0.102.0
VSCode Version: 1.96.2 (Universal)
Electron: 32.2.6
ElectronBuildId: 10629634
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Darwin arm64 23.6.0

Keyboard Shortcuts Troubleshoot

ctrl+p (not work)
2025-01-16 11:38:43.189 [info] [KeybindingService]: / Received  keydown event - modifiers: [ctrl], code: KeyP, keyCode: 80, key: p
2025-01-16 11:38:43.189 [info] [KeybindingService]: | Converted keydown event - modifiers: [ctrl], code: KeyP, keyCode: 46 ('P')
2025-01-16 11:38:43.189 [info] [KeybindingService]: | Resolving ctrl+[KeyP]
2025-01-16 11:38:43.190 [info] [KeybindingService]: \ From 6 keybinding entries, no when clauses matched the context.
2025-01-16 11:38:43.489 [info] [KeybindingService]: + Ignoring single modifier ctrl due to it being pressed together with other keys.
ctrl+b (work)
2025-01-16 11:39:59.431 [info] [KeybindingService]: / Received  keydown event - modifiers: [ctrl], code: KeyB, keyCode: 66, key: b
2025-01-16 11:39:59.431 [info] [KeybindingService]: | Converted keydown event - modifiers: [ctrl], code: KeyB, keyCode: 32 ('B')
2025-01-16 11:39:59.434 [info] [KeybindingService]: | Resolving ctrl+[KeyB]
2025-01-16 11:39:59.434 [info] [KeybindingService]: \ From 1 keybinding entries, no when clauses matched the context.
2025-01-16 11:39:59.694 [info] [KeybindingService]: + Ignoring single modifier ctrl due to it being pressed together with other keys.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named. Start by reproducing the PR text area behavior on macOS with ctrl+p and ctrl+f, then inspect the keyboard shortcut troubleshooting output and the extension's PR text area entry point. Done means both shortcuts move the cursor while the reported working shortcuts remain functional.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, typescript, vscode
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.