actualbudget/actual

[Bug]: When renaming a category in Firefox, the cursor cannot be moved using the mouse pointer

Open

#5620 opened on Aug 24, 2025

View on GitHub
 (2 comments) (1 reaction) (0 assignees)JavaScript (7,129 stars) (603 forks)batch import
budgetingbughelp wanteduser interface

Description

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

In Firefox, I cannot click to place my cursor when I try to rename a budget category. I have to use the arrow keys to move the cursor. I can do it in Microsoft Edge, so I believe it is a bug only in Firefox.

How can we reproduce the issue?

Using the Firefox browser, try to rename a category and click somewhere in the middle of the text box to place the cursor there. Nothing happens.

Where are you hosting Actual?

Fly.io

What browsers are you seeing the problem on?

Firefox

Operating System

Windows and macOS

Contributor guide

Tech stack
javascriptcss
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
basic understanding of browser event handling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Investigate the input field used for renaming categories (likely in components like `CategoryInput` or similar). The issue is specific to Firefox, so focus on differences in mouse event handling. Look for event listeners on the input field that might interfere with click to place cursor. Consider CSS properties like `user select` or `pointer events`. Check if there is any custom selection logic that disables default browser behavior. Reproduce the bug locally in Firefox and debug with the browser's developer tools.