[MGNLFORM-29] Form - Validation - CSS Optimization Created: 31/Aug/09  Updated: 27/Nov/13  Resolved: 15/Sep/09

Status: Closed
Project: Magnolia Form Module
Component/s: None
Affects Version/s: 1.0.1
Fix Version/s: 1.0.3

Type: Bug Priority: Major
Reporter: Rainer Blumenthal Assignee: Teresa Miyar
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File patch-CSS.txt    
Template:
Patch included:
Yes
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Non valid "Text field group"-elements show up in a bad way after validation.

Problem: If there is a non-valid element, it only gets the CSS-class "error". Different CSS-Klassen (e.g. "s", "m" oder "l") are not being added.

Lösung: Additional style-Properties should be set after the class "error" is set (info.magnolia.module.form.paragraphs.models.FormFieldModel)

Please have a look at the attached patch.



 Comments   
Comment by Christoph Meier [ 27/Nov/13 ]

It is resolved and very old.

Generated at Mon Feb 12 05:36:09 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.