pingdotgg / pingdotgg/t3code

[Bug]: Can't change Keybindings

Open
#11,448 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

accepted bug via-triage
Dominant language
TypeScript
Stars
23k
Forks
5.9k
Avg merge
11h 14m
Merged PRs (30d)
357

Description

Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/web

Steps to reproduce
  1. Open app.t3.codes
  2. go to keybindings
  3. try to change anything (either change the hotkey for a keybinding or the 'when' condition)
  4. click save... nothing happens and "save" button is still there
Expected behavior

Keybindings to update or some warning/error to appear telling me what's happening

Actual behavior

No feedback whatsoever. The blue "Save" button still exists despite clicking it infinite times.

Attached is me trying to change multiple keybindings (first is hotkey, second is the condition)

Image Image

This image is the network call after clicking the "Save" button 25 times. No network call is happening:

Image

This image is the console after clearing it then clicking the "Save" button another 25 times. No console log is appearing (except a cookie error message that is related to the timing of me clicking the save button)

Image
Impact

Minor bug or occasional failure

Version or commit

v0.0.40 web

Environment

Firefox 154.0 (64-bit)

Logs or stack traces
None. Except for the probably irrelevant console log:

Cookie “_cfuvid” has been rejected for invalid domain. touch
Cookie “_cfuvid” has been rejected for invalid domain. touch
Screenshots, recordings, or supporting files

No response

Workaround

None. I have to deal with default keybindings despite conflicting with important terminal keyboard shortcuts.

Contributor guide

Open the contributing guide

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

Start in apps/web by reproducing the keybindings save failure in Firefox 154. Inspect the save interaction and verify whether clicking it triggers a request or error. Done means changed hotkeys or conditions persist, or the interface clearly reports why saving failed.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
62/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.