keepassxreboot/keepassxc

& not rendering in name of database tab

Closed

#12,037 opened on Apr 23, 2025

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)C++ (1,797 forks)batch import
good first issueuser interface

Repository metrics

Stars
 (27,139 stars)
PR merge metrics
 (Avg merge 19d 12h) (17 merged PRs in 30d)

Description

Have you searched for an existing issue?

  • Yes, I tried searching and reviewed the pinned issues

Brief Summary

I noticed that when I go to database settings and set the database name to something with and & the & is not showing in the name on the database tab. Tested characters like # and @ they show up correctly.

Image

Image

Image

Steps to Reproduce

  1. Got to database settings of a database
  2. Change the database name to something with and & in it. For instance Test & Test
  3. If the tab is not showing open a second database so tabs show and notice an empty space where there should be an &

Expected Versus Actual Behavior

Expected to see the & in the name but i'm seeing an empty space instead.

KeePassXC Debug Information

KeePassXC - Version 2.7.10
Revision: b342be4

Qt 5.15.11
Debugging mode is disabled.

Operating system: Windows 11 Version 2009
CPU architecture: x86_64
Kernel: winnt 10.0.26100

Enabled extensions:
- Auto-Type
- Browser Integration
- Passkeys
- SSH Agent
- KeeShare
- YubiKey
- Quick Unlock

Cryptographic libraries:
- Botan 3.1.1

Operating System

Windows

Linux Desktop Environment

None

Linux Windowing System

None

Contributor guide

Research direction
The bug is likely caused by Qt interpreting '&' as an accelerator prefix in widget text. To fix, the ampersand in the database name should be escaped as '&&' when setting the tab title. Look for where the tab name is set, possibly in src/gui/DatabaseWidget.cpp or similar. Check if the tab text is set via setTabText or setText; if so, ensure the string is escaped using Qt::escape or by replacing '&' with '&&'.
Tech stack
cpp
Domain
desktop
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.
Under 1 hour
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.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80