dotCMS / dotCMS/core

UVE: Remove `loading` state when page does not emit the `CLIENT_IS_READY` event

Open
#31,219 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

OKR : User Experience Priority : 3 Average Team : Scout Type : Task
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Parent Issue

#30943

Issue

https://github.com/user-attachments/assets/823d36b7-825e-497e-9313-262ffa192624

Task

```[tasklist]

  • The Initial loading state should be removed even if the page does not emit the CLIENT*IS*READY event
  • Do not let the user edit the page before the load is completed
    \`
Proposed Objective

OKR: User Experience

Proposed Priority

Priority 3 - Average

Acceptance Criteria
  • The Initial loading state should be removed even if the page does not emit the CLIENT_IS_READY event
  • The user is not able to edit before the Page is fully loaded
Assumptions & Initiation Needs

I think we can use the onLoad event of the iframe. Once the iframe says it is ready, we can safely remove the loading

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 locating the UVE page iframe and the handling for the CLIENT_IS_READY event. Check how the iframe onLoad event relates to the initial loading state, then verify that loading ends when the event is absent while editing remains disabled until the page is fully loaded.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.