RetroAchievements/RAWeb

Achievement Tabs delete written Comment

Open

#4,737 opened on Apr 5, 2026

View on GitHub
 (5 comments) (0 reactions) (0 assignees)PHP (130 forks)auto 404
area/uigood first issuekind/enhancement

Repository metrics

Stars
 (413 stars)
PR merge metrics
 (PR metrics pending)

Description

Describe the bug Since a few days we now have a new achievement page that has tabs for Comments, Recent Unlocks and Changelog split. Today I realized that acomment you write does not get temporarily saved when switching the tabs meaning if you swap back to the Comments section, whatever you wrote but not submit yet is just deleted.

To Reproduce Steps to reproduce the behavior:

  1. Visit any achievement page
  2. Write any comment BUT DO NOT submit it yet
  3. Switch to Recent Unlocks or Changelog
  4. Switch back to Comments
  5. Your comment your were about to post is gone and needs to be rewritten

Expected behavior In my opinion the text you previously wrote should still be there after switching tabs. There are several reasons why people could switch tabs mid-writing. For example they want to reference to another user who got an unlock and switch to the tab to make sure they spell the name correctly, or they want to mention a recent change that happened and want to check the date or time when it happened. There is no warning that the message will be gone and it is frustrating if you write like 2 minutes of a message just to have it disappear the next second and needing to rewrite it.

Contributor guide

Research direction
Investigate the tab switching implementation in the achievement page. Look for how the comment textarea state is managed. Check if the state is stored in a JavaScript variable or if it uses a form that gets cleared when switching tabs. Identify where the text content is lost and propose a solution to persist the comment text across tab switches.
Tech stack
phpjavascript
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitPHPJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65