refactor: normalize keyboard scope handling

barrettruth commented

2026-05-11 19:20:27 +00:00

Owner

Parent: #355

Problem

Keyboard behavior is still distributed across global, queue, kanban, calendar, settings, popovers, dialogs, and task-detail handlers. Keymap customization is gone, so the remaining keyboard code should be simpler and explicit about scope, focus rules, browser shortcuts, counts, and operator-style sequences.

Solution

Introduce a shared keyboard scope helper while preserving current fixed bindings:

centralize input-focus and browser-shortcut guard behavior
make handler registration/scope explicit for dialogs, task panel, calendar, and global navigation
keep fixed keymap metadata and shortcut help intact
avoid reintroducing customization storage or UI

Acceptance criteria

Keyboard handlers share guard and scope rules instead of each reimplementing them.
Existing fixed shortcuts keep working.
Dialog/task-panel focus behavior does not regress.
Tests cover the helper contract and one representative scoped handler.

Parent: #355 ## Problem Keyboard behavior is still distributed across global, queue, kanban, calendar, settings, popovers, dialogs, and task-detail handlers. Keymap customization is gone, so the remaining keyboard code should be simpler and explicit about scope, focus rules, browser shortcuts, counts, and operator-style sequences. ## Solution Introduce a shared keyboard scope helper while preserving current fixed bindings: - centralize input-focus and browser-shortcut guard behavior - make handler registration/scope explicit for dialogs, task panel, calendar, and global navigation - keep fixed keymap metadata and shortcut help intact - avoid reintroducing customization storage or UI ## Acceptance criteria - Keyboard handlers share guard and scope rules instead of each reimplementing them. - Existing fixed shortcuts keep working. - Dialog/task-panel focus behavior does not regress. - Tests cover the helper contract and one representative scoped handler.

barrettruth added this to the v0.1.0 milestone

2026-05-11 19:20:27 +00:00

barrettruth added the

track:core

track:ui

type:cleanup

labels

2026-05-11 19:20:27 +00:00

barrettruth referenced this issue

2026-05-11 19:20:49 +00:00

tracker: blank-start cleanup and foundation migration #305

barrettruth referenced this issue

2026-05-11 19:21:09 +00:00

ui cleanup after scope reduction #239

barrettruth referenced this issue

2026-05-11 19:25:33 +00:00

product: restore keybinding discoverability after customization removal #328

barrettruth referenced this issue from a pull request that will close it,

2026-05-11 20:18:24 +00:00

refactor: normalize keyboard scope handling #349

barrettruth closed this issue

2026-05-11 20:19:02 +00:00

barrettruth referenced this issue from a commit

2026-05-11 20:19:03 +00:00

refactor: normalize keyboard scope handling (#349)

barrettruth commented

2026-05-11 21:02:03 +00:00

Author

Owner

Reopening under #355. The first keyboard cleanup closed part of the old tracker, but current main still repeats keyboard scope/guard handling across global, queue, kanban, calendar, settings, and dialogs. This issue now tracks the shared helper follow-up only.

barrettruth reopened this issue

2026-05-11 21:02:04 +00:00

barrettruth referenced this issue

2026-05-11 21:02:45 +00:00

tracker: foundation hardening before Google sync #355

~~barrettruth referenced this issue 2026-05-12 12:45:24 +00:00~~

refactor: normalize keyboard scope handling #382

barrettruth referenced this issue from a pull request that will close it,

2026-05-12 12:45:51 +00:00

refactor: normalize keyboard scope handling #382

barrettruth closed this issue

2026-05-12 12:54:28 +00:00