Issue Task Under Review

#109860Remove frontend class properties from Form framework configuration

Josua Vogel 05/21/26, 20:17 updated 11/19/26, 11:40

Description

This change removes all CSS class property definitions from the YAML configuration files of the EXT:form framework’s form elements, as well as the fieldProperties and formNavigation rendering options from the root Form.yaml. The corresponding Fluid frontend templates are updated to use hardcoded CSS class names instead of dynamically reading them from YAML properties.

Intention

Previously, CSS classes applied by the frontend templates (e.g. form-control, is-invalid, form-label, form-text, etc.) were stored as configurable properties in the YAML definitions of each form element and in the global renderingOptions of the form. The Fluid templates dynamically resolved these class names at render time via property lookups like {element.properties.elementClassAttribute} or {element.rootForm.renderingOptions.fieldProperties.errorClassAttribute}.
This relationship created an indirect coupling between the YAML configuration layer and the frontend rendering layer, making it harder to understand how HTML output is produced and which configuration actually influences the DOM.

Benefits

  • Improved clarity: Frontend templates are now self-contained and readable without needing to cross-reference YAML files to understand which CSS classes are applied.
  • Reduced configuration complexity
  • Cleaner separation of concerns: The YAML layer defines form behaviour and structure; the Fluid layer owns the rendering output including CSS classes.
  • Easier customisation: Integrators who want to change frontend styling are now clearly directed to override Fluid templates rather than patching YAML class attributes scattered across dozens of files.

Reviews 1

History 08