Skip to content

Fix last press timekeeping#6

Merged
ty2k merged 1 commit into
mainfrom
bugfix/capslock-mode
Jun 1, 2026
Merged

Fix last press timekeeping#6
ty2k merged 1 commit into
mainfrom
bugfix/capslock-mode

Conversation

@ty2k

@ty2k ty2k commented Jun 1, 2026

Copy link
Copy Markdown
Owner

This fixes the broken logic in how last presses are tracked in the handleShiftOrCapsPress(), fixing the failing test from this test suite run.

Without this change, shift keys work as expected, but shift-or-caps and caps only work as one-shot shift buttons, not to keep a persistent caps lock.

@ty2k ty2k self-assigned this Jun 1, 2026
@ty2k ty2k added the bug Something isn't working label Jun 1, 2026
@ty2k ty2k requested a review from Copilot June 1, 2026 02:56

Copilot AI 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.

Pull request overview

Fixes shift-or-caps double-press timekeeping so the second press can correctly toggle persistent caps lock mode (matching the intended mobile-keyboard behavior and unblocking the failing test run referenced in the PR description).

Changes:

  • Record the timestamp of the most recent shift-or-caps press (instead of clearing it), enabling double-press detection for caps lock toggling.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread src/react/src/lib/Keyboard.tsx
@ty2k ty2k merged commit e229e1d into main Jun 1, 2026
2 checks passed
@ty2k ty2k deleted the bugfix/capslock-mode branch June 1, 2026 03:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants