actualbudget / actualbudget/actual

[Bug]: Enter Key Behavior

Aperta Adatta ai principianti
#8,460 1 commento 0 reazioni 0 assegnatari Vedi su GitHub
budgeting help wanted
Lingua principale
TypeScript
Stelle
28.8k
Fork
3k
Merge medio
2g 11h
PR unite (30g)
65

Descrizione

### What happened?

I was entering numbers for my Categories on the Budget Screen. I insert the amount and press Enter to advance to the next Category. However, the behavior is not consistent. When I get to the 8th category, the cursor does not move down to the next Category. Also the 10th Category, so the pattern is random. Additionally, the cursor does not always move down to the next Category Group when I press Enter.

### How can we reproduce the issue?

Navigate to the Budget tab.
Enter $100 in the first 7 Budgeted fields
press Enter key or Tab key to automatically advance to the next Budgeted field.
Enter $100 in the 8th Budgeted field
press Enter
Observe the cursor does not advance to the next category.
Enter $100 in the last Category for the Group
Press Enter
Notice the cursor does not advance to the next Category in the next Group. Sometimes the cursor will advance to the next group.

### Where are you hosting Actual?

Pikapods

### What browsers are you seeing the problem on?

Desktop App (Electron)

### Operating System

Mac OSX

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

Reproduce in the Electron desktop app by opening the Budget tab and stepping through Budgeted fields with Enter/Tab as described (especially 7th, 8th, and end-of-group positions). Then find the Budget screen UI code that handles keyboard input and moves focus to the next Budgeted field/group. Check the boundary logic where category index/group index is advanced and ensure it always computes a valid next target. Done when manual checks show Enter consistently jumps to the expected next field every time.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
electron, typescript
Ambito
desktop, frontend
Tipo di issue
Bug
Difficoltà
2/5
Tempo stimato
1-3 ore
Stato di attività
Tranquilla
Chiarezza
Abbastanza chiara
Idoneità per principianti
68/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.