New Edit Content: validation errors jump between tabs and the error banner stays after the next action

Aperta
#38,655 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
72/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
angular, java, typescript
Ambito
frontend, testing

Direzione di ricerca

Start with core-web/libs/edit-content/src/lib/store/features/form/form.feature.ts and dot-edit-content-form.component.ts, then trace how validation state is retained across tab changes and cleared after a successful workflow action. Reproduce with a content type that has required fields on two tabs and run the relevant form tests. Done means both tabs keep their error indicators until valid, the banner clears after success or error resolution, and tests cover both behaviours.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

dotCMS: New Edit Contentlet Team : Scout Type : Defect
Problem Statement

When a save fails validation on a content type with several tabs, the error state moves as the author switches tabs: fields in the first tab lose their error marker when the second tab is shown and regain it later, which reads as "jumping". Separately, the error banner shown at the top of the form stays visible after the author fixes the fields and runs the next workflow action successfully. Both were reported in #feat-edit-content (July and October 2026) and were deferred as not blocking GA.

Steps to Reproduce
  1. Create a content type with two tabs and a required field in each; enable the new editor.
  2. Open a new contentlet, leave both required fields empty, click Save.
  3. Switch between the two tabs and watch the error markers.
  4. Fill both fields and click Save again.

Expected: markers stay on both fields regardless of the active tab; the banner disappears after the successful save. Actual: markers flicker per tab; the banner remains.

Acceptance Criteria
  • Error markers and tab indicators are stable across tab switches until the field is valid.
  • The error banner is cleared when a workflow action succeeds or when all errors are resolved.
  • Spec covers both behaviours.
dotCMS Version

main (2026-11-18)

Severity

Minor

Links
  • #38634 pillar; related adoption ticket #38174 (required field in inactive tab)
  • Code: core-web/libs/edit-content/src/lib/store/features/form/form.feature.ts, dot-edit-content-form.component.ts
Lingua principale
Java
Stelle
972
Fork
493
Merge medio
2g 12h
PR unite (30g)
228

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di dotCMS/core

Tutte le issue di dotCMS/core

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.