[MGNLUI-7214] Using multifield component breaks indenting on Stories App Created: 07/Jun/22 Updated: 18/Jul/23 Resolved: 02/Jun/23 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | content app |
| Affects Version/s: | 6.2.19 |
| Fix Version/s: | 6.3.0, 6.2.35 |
| Type: | Bug | Priority: | Normal |
| Reporter: | Roberto Gaona | Assignee: | Robert Šiška |
| Resolution: | Fixed | Votes: | 2 |
| Labels: | DevX_AuthX_Support | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||
| Task DoD: |
[X]*
Doc/release notes changes? Comment present?
[X]*
Downstream builds green?
[X]*
Solution information and context easily available?
[X]*
Tests
[X]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||
| Bug DoR: |
[X]*
Steps to reproduce, expected, and actual results filled
[X]*
Affected version filled
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Visible to: |
Chuck Aksamit
|
||||||||||||||||
| Epic Link: | Support | ||||||||||||||||
| Story Points: | 3 | ||||||||||||||||
| Team: | |||||||||||||||||
| Work Started: | |||||||||||||||||
| Approved: |
Yes
|
||||||||||||||||
| Description |
|
Using the attached light module (test), when trying to add a Video block on a story from the Stories app and adding an entry of the jcrMultiField component makes it wrongly indented:
|
| Comments |
| Comment by Chuck Aksamit [ 11/May/23 ] |
|
This is a pretty important issue for us at Crescendo Collective. We have multiple clients with many apps built as custom content apps and this edge case around blocks, multifield and nesting is hard to resolve without a significant amount of customization. The indenting is visually jarring... But when these fields have blocks nested within them the controls are impossible to distinguish without intimate knowledge of the blocks and their nesting configuration which the content authors do not have. We found a partial work around by nesting in yet another container field for collapsible composites from 5 UI but it adds unneeded UI functionality, isn't a perfect fix and further complicates configuration. Please prioritize this issue as developing content apps that support things like rich content in accordion, carousel or even just more than one column looks very bad in the authoring interface. Please also see my support ticket SUPPORT-16418 for more examples. |
| Comment by Christopher Zimmermann [ 17/May/23 ] |
|
Are we sure that this has something to do with using the `!include` directive? Or is it rather.a general problem with multifield in the stories app? I just want to ask because I have not heard of an `include` directive having an impact in this way before. |
| Comment by Roberto Gaona [ 17/May/23 ] |
|
Hello Christopher, Just ran a quick test and you are right, this issue also appears without the !include directive, so it's more an issue with multifields on stories rather than with the include. Kind regards, Roberto Gaona |
| Comment by Chuck Aksamit [ 17/May/23 ] |
|
I also don't think it's related to !include directives. The multifields in my examples from the SUPPORT-16418 ticket are there to provide the nested block containers - so columns, carousel items, tabs, etc. - and if they are excluded the controls are just displayed differently but are still just as hard to distinguish to the editor. We also notice that nested fields change in width as the editor adjusts the nested block configuration. With some rendering very narrow on first load and then getting wider as other sibling blocks are added. I can provide further detail in the form of demos, configuration examples, screenshots and more if needed to help see the issue here and resolve it. Also open to having a call to show these from a local/dev environment. Just let me know! |
| Comment by Thomas Duffey [ 19/Jun/23 ] |
|
We put this through testing and unfortunately the update is unusable. In certain cases of nesting the standard controls for adding blocks are now missing making it impossible to manage content. |