dotCMS / dotCMS/core

Pressing ESC to abandon asset edit locks the UI — requires new tab to recover

Open
#35,415 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

OKR : Customer Support Team : Maintenance
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Problem Statement

Pressing the Escape key to cancel out of an asset/file editor (most notably VTL files)
leaves the entire dotCMS authoring UI in a locked, unresponsive state. The interface
cannot be recovered without opening a new tab.

Steps to Reproduce

https://drive.google.com/file/d/1Sb-J43-IagVdLeWOs_Je-NHoIeRJBXWj/view?usp=drive_link

Steps to Reproduce

  1. Navigate to a VTL file (or other asset) in the dotCMS authoring UI
  2. Double-click to open the file/asset editor
  3. Press the Escape key to back out without saving
Acceptance Criteria

Expected Behavior

The editor closes and the user is returned to the normal, functional UI state.

Actual Behavior

The entire authoring interface becomes locked and unresponsive. Manual refresh does
not recover it — the user must open a new browser tab to continue working.

dotCMS Version

26.04.21-01

Severity

Medium - Some functionality impacted

Links

https://helpdesk.dotcms.com/a/tickets/36725

https://helpdesk.dotcms.com/a/tickets/36747

Contributor guide

Open the contributing guide

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.

Research direction

Start by reproducing the Escape-key flow in the dotCMS authoring UI with a VTL file or other asset, using the linked recording as context. Trace the asset editor's cancel and Escape handling to identify why the UI remains locked; done means the editor closes and the authoring interface remains responsive without opening a new tab.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.