[GH-ISSUE #5261] [Bug]: Glitchy focus issues in filter popups #16480

Closed
opened 2026-04-14 19:33:22 -05:00 by GiteaMirror · 3 comments
Owner

Originally created by @mullermn on GitHub (Jun 30, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/5261

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

Depending on the sequence of actions the user takes a return key used during filter creation can close the popup and create a filter without capturing the value the user typed.

This applies in both web and electron apps at v25.6.1

How can we reproduce the issue?

  1. In All Accounts click Filter/Category/Contains then type some text - it will appear in the free text field.
  2. Press return
  3. User expectation is that the value they typed will be used as a substring for a 'contains' filter, but what actually happens is that 'nothing' is captured.
    Image

Image

As an example of how unintuitive this is, if the user completes step 1, then clicks to a different window, then returns focus to the Actual window by clicking the window chrome (not even the data area), or alt-tabbing, then the return key behaves as expected:

Image

This applies in both the electron app and the web app

Where are you hosting Actual?

Pikapods

What browsers are you seeing the problem on?

Desktop App (Electron)

Operating System

Mac OSX

Originally created by @mullermn on GitHub (Jun 30, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/5261 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? Depending on the sequence of actions the user takes a return key used during filter creation can close the popup and create a filter without capturing the value the user typed. This applies in both web and electron apps at v25.6.1 ### How can we reproduce the issue? 1) In All Accounts click Filter/Category/Contains then type some text - it will appear in the free text field. 2) Press return 3) User expectation is that the value they typed will be used as a substring for a 'contains' filter, but what actually happens is that 'nothing' is captured. ![Image](https://github.com/user-attachments/assets/e4baa55d-e807-44f4-aa27-2f355adbbf74) ![Image](https://github.com/user-attachments/assets/8bd21261-d988-4ce9-aa1a-5c7125483242) As an example of how unintuitive this is, if the user completes step 1, then clicks to a different window, then returns focus to the Actual window by clicking the window chrome (not even the data area), or alt-tabbing, then the return key behaves as expected: ![Image](https://github.com/user-attachments/assets/09dccef1-612e-4619-a7fe-ce3e39e966ef) This applies in both the electron app and the web app ### Where are you hosting Actual? Pikapods ### What browsers are you seeing the problem on? Desktop App (Electron) ### Operating System Mac OSX
GiteaMirror added the user interfacegood first issuebug labels 2026-04-14 19:33:22 -05:00
Author
Owner

@mushrafmim commented on GitHub (Jul 2, 2025):

Hi, I would love to work on this issue.

<!-- gh-comment-id:3026056298 --> @mushrafmim commented on GitHub (Jul 2, 2025): Hi, I would love to work on this issue.
Author
Owner

@mushrafmim commented on GitHub (Jul 2, 2025):

When using the button, there are no issues. When using the Return key it produces the error always. I am trying to fix this.

<!-- gh-comment-id:3026133328 --> @mushrafmim commented on GitHub (Jul 2, 2025): When using the button, there are no issues. When using the `Return` key it produces the error always. I am trying to fix this.
Author
Owner

@AsgerMogensen commented on GitHub (Mar 14, 2026):

Duplicate of issue #5228 fixed in v25.8.0 with PR #5263

<!-- gh-comment-id:4061115831 --> @AsgerMogensen commented on GitHub (Mar 14, 2026): Duplicate of issue #5228 fixed in v25.8.0 with PR #5263
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#16480