Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Switching programming languages clears editor undo history

Open
#365 1 comment 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@Chingyong0905 is already working on this.

Since Oct 19, 2026.

Assessment

This issue has not been assessed yet.

Description

Observed behavior

Switching programming languages clears the code editor's undo history, even though the code itself is preserved.

As a result, users cannot undo previous edits or recover accidentally deleted code after switching back to the original language.

Expected behavior

Each programming language should retain its own undo/redo history when switching between languages during an interview.

Reproduction
  1. Start a coding interview, select Python (for example), and enter a few lines of code.
  2. Delete a line and press Ctrl+Z to confirm that undo works.
  3. Delete the line again.
  4. Switch to any other supported programming language, then switch back to Python.
  5. Press Ctrl+Z again. The deleted line can no longer be restored after switching back to Python.
    This issue occurs regardless of which programming language is selected during the switch.
CodeTrial version

codetrial 0.1.0 (5b4d8c7)

Environment

OS: Windows 11 Home Single Language, Version 25H2 (Build 26200.9711)
Browser: Google Chrome 155.0.8059.80 (64-bit)
Language: All supported programming languages (Python, JavaScript, C, C++, Java)
Interview loop: Coding interview
Problem: Sensor Calibration Index (LeetCode 108)
REACTO or STAR step: Code
Reconnect: None

Sanitized evidence

No response

Public data confirmation
  • I removed credentials, session tokens, candidate recordings, and personal interview content from this public report.
Dominant language
Rust
Stars
177
Forks
100
Avg merge
1d 10h
Merged PRs (30d)
135

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sysprog21/codetrial

All issues in sysprog21/codetrial

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.