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

Abierto
#38,655 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
72/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
angular, java, typescript
Área
frontend, testing

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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
Lenguaje dominante
Java
Estrellas
972
Forks
493
Merge medio
2 d 12 h
PR fusionados (30 d)
228

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de dotCMS/core

Todos los issues de dotCMS/core

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.