[MGNLUI-3645] Make sure CKEditor component's requirement state is respected in UI Created: 06/Nov/15  Updated: 21/Mar/16  Resolved: 18/Mar/16

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 5.4.3
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Sang Ngo Huu
Resolution: Fixed Votes: 2
Labels: support
Remaining Estimate: 2d 5h
Time Spent: 1d 3h
Original Estimate: 4d

Issue Links:
Relates
relates to MGNLUI-3620 Required field within a complex field... Closed
duplicate
is duplicated by MGNLUI-3662 The icon marking a required field doe... Closed
Template:
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:
Sprint: Saigon 35
Story Points: 8

 Description   

For some reason the shared state of CKEditorTextField does not extend the AbstractFieldState (on the server-side it does!) and hence it lack such fields as 'isRequired' making it hard to reflect in UI (no requirement asterisk is rendered).

We need to find the way to work this around.



 Comments   
Comment by Jan Haderka [ 06/Nov/15 ]

IIRC, there was issue w/ default config that even when you didn't edit the field, it still saved <p></p> thus making field pass the "isRequired" test w/ false positive.

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