[Bug]: On a "new transaction" mobile page clicking "payee" takes two clicks instead of one #1340

New Issue

GiteaMirror · 2026-02-28T19:40:52-06:00

GiteaMirror commented

2026-02-28 19:40:52 -06:00

Originally created by @minajevs on GitHub (Aug 15, 2024).

Verified issue does not already exist?

I have searched and found no existing issue
I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file)

What happened?

When on mobile, on a "new transaction" page clicking on any form field (payee, category, account, date, notes) takes 2 clicks to open the field instead of 1.

Looks like amount field is focused by default, and then first click outside unfocuses the amount field, and requires second click to focus another element. Instead it should immediately switch focus to another clicked element.

See recording:

https://github.com/user-attachments/assets/fbe9d80b-4382-466d-846f-5ca6d24c1330

Where are you hosting Actual?

Pikapods

What browsers are you seeing the problem on?

Firefox, Chrome, Safari

Operating System

Mobile Device

Originally created by @minajevs on GitHub (Aug 15, 2024). ### Verified issue does not already exist? - [X] I have searched and found no existing issue - [X] I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file) ### What happened? When on mobile, on a "new transaction" page clicking on any form field (payee, category, account, date, notes) takes 2 clicks to open the field instead of 1. Looks like amount field is focused by default, and then first click outside unfocuses the amount field, and requires second click to focus another element. Instead it should immediately switch focus to another clicked element. See recording: https://github.com/user-attachments/assets/fbe9d80b-4382-466d-846f-5ca6d24c1330 ### Where are you hosting Actual? Pikapods ### What browsers are you seeing the problem on? Firefox, Chrome, Safari ### Operating System Mobile Device

GiteaMirror added the user interface responsive bug help wanted labels 2026-02-28 19:40:52 -06:00

GiteaMirror commented

2026-02-28 19:40:52 -06:00

@minajevs commented on GitHub (Aug 15, 2024):

Can I try to fix the issue myself? I am interested in contributing :)

@minajevs commented on GitHub (Aug 15, 2024): Can I try to fix the issue myself? I am interested in contributing :)

GiteaMirror commented

2026-02-28 19:40:53 -06:00

@youngcw commented on GitHub (Aug 15, 2024):

Can I try to fix the issue myself? I am interested in contributing :)

Go ahead if you want to try

@youngcw commented on GitHub (Aug 15, 2024): > Can I try to fix the issue myself? I am interested in contributing :) Go ahead if you want to try

GiteaMirror commented

2026-02-28 19:40:53 -06:00

@MatissJanis commented on GitHub (Mar 19, 2025):

👋 This might be fixed already in one of the latest versions. Would you mind verifying @minajevs ?

@MatissJanis commented on GitHub (Mar 19, 2025): 👋 This might be fixed already in one of the latest versions. Would you mind verifying @minajevs ?

GiteaMirror commented

2026-02-28 19:40:53 -06:00

@minajevs commented on GitHub (Mar 20, 2025):

👋 This might be fixed already in one of the latest versions. Would you mind verifying @minajevs ?

Just tested on https://demo.actualbudget.org/transactions/new and it is still actual (hehe).

My PR, unfortunately, was closed as stale without a review, and quickly going thought the updates to the code in the latest releases, there doesn't seem to be any related fixes.

I have also decided not to migrate to Actual since then, so I doubt I will have time/energy to refresh the PR. Anyone is welcome to pick it up and try again.

@minajevs commented on GitHub (Mar 20, 2025): > 👋 This might be fixed already in one of the latest versions. Would you mind verifying [@minajevs](https://github.com/minajevs) ? Just tested on https://demo.actualbudget.org/transactions/new and it is still actual (hehe). My PR, unfortunately, was closed as stale without a review, and quickly going thought the updates to the code in the latest releases, there doesn't seem to be any related fixes. I have also decided not to migrate to Actual since then, so I doubt I will have time/energy to refresh the PR. Anyone is welcome to pick it up and try again.