Skip to content

feat(reader): add keyboard navigation with settings toggle#133

Merged
LeslieLeung merged 2 commits into
mainfrom
feature/keyboard-navigation
Jun 11, 2026
Merged

feat(reader): add keyboard navigation with settings toggle#133
LeslieLeung merged 2 commits into
mainfrom
feature/keyboard-navigation

Conversation

@LeslieLeung

Copy link
Copy Markdown
Owner

Enable arrow keys and j/k to move between entries in the reader, with an appearance setting to turn it off and merged user settings updates.

Originally purposed in #117 and credits to @GoToBoy.

Enable arrow keys and j/k to move between entries in the reader, with an appearance setting to turn it off and merged user settings updates.

Co-authored-by: Cursor <cursoragent@cursor.com>

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 16042c9a2f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +398 to +402
if (
target.tagName === 'INPUT' ||
target.tagName === 'TEXTAREA' ||
target.isContentEditable
) {

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Ignore keyboard events from focused controls

When focus is on ReaderPage controls that are not inputs, such as the filter DropdownMenu trigger/items, ArrowUp/ArrowDown events can still bubble to this document handler because only inputs, textareas, and contenteditable targets are excluded. In that state, using the menu's normal keyboard navigation also selects the previous/next article and calls preventDefault, so keyboard users cannot reliably operate the filter menu or other focused buttons without unexpectedly changing the current entry.

Useful? React with 👍 / 👎.

…rols

Arrow keys no longer hijack entry navigation when focus is on a button,
link, select, or any element inside an ARIA widget (menu, listbox,
combobox, dialog, etc.), allowing filter dropdowns and other controls
to handle their own keyboard events without interference.

Co-authored-by: Cursor <cursoragent@cursor.com>
@LeslieLeung LeslieLeung merged commit 4708f5a into main Jun 11, 2026
2 checks passed
@LeslieLeung LeslieLeung deleted the feature/keyboard-navigation branch June 11, 2026 06:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant