[MGNLUI-7361] Configure Global validator configuration to allow default RichTextField options Created: 14/Jul/22 Updated: 25/Nov/22 |
|
| Status: | Open |
| Project: | Magnolia UI |
| Component/s: | dialogs |
| Affects Version/s: | 6.2.21 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Roberto Gaona | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| 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)
|
||||
| Date of First Response: | |||||
| Epic Link: | richTextField HTML validation | ||||
| Team: | |||||
| Description |
|
At the current status, the recently introduced "Global validator" feature, collides with the default RichTextEditor definition and marks as invalid or malicious some parameters that can be added from the editor (class, target attributes...). For example, inserting a link with any of the advanced options ends up on this message. It would be great if the configuration provided by default, took into account all those cases. As a workaround, any user can manually validate the elements or properties he wants to use with easiness by modifying its configuration. |