The pictograph is squeezed on the top of the box, the text wrapping is suboptimal.
Maybe working with tables within the boxes is an option? An optional text within the header might help with accessability (i´m not an expert in this topic)?
Hi!
We had complications when implementing the message boxes, which ended up in a small change from our design goal (which had similar lining up for the icon and text boxes).
The text is divided by “enter”, which is represented in a table-view (horizontal ). Is it possible to divide text-passages in paragraphs (vertical)?
== 12.3 Infobox ==
{{info}}
**Dieses Feld ("Infobox") wird genutzt, um Beispiele zu beschreiben.**
Damit ist es möglich Sachverhalte zu illustrieren indem konkrete Beispiele für Listen, Quellcode,... angezeigt werden.
{{/info}}
They all have a new line inside of them, so there’s something to fix.
Edit: It’s the first one that has a couple of spaces on the empty line, not the second one.
When there’s just an empty line, the renderer already considers that there’s two different paragraphs (which is correct) , and they are not wrapped inside a common <p> (during manual testing, I did not cover usage of the macro in these conditions - which is a mistake). Those paragraphs are positioned with the same flex used to position the icon, title and image, which means -on the same line-.
I setup a testing page with a bit more variety in conditions.
It seems like this issue cannot be reproduced either when there’s a title or a picture for the info box.
@Roland In order to fix this, you have three solutions (from easiest to most difficult):
Get the patch in a migration of your wiki (could take some time, but it should be in the next 16.10 release)
Use only one HTML paragraph in your info messasge content. The second one is created only when there’s a fully empty line (hard to scale or migrate if you already have a bunch of those).
Build the xwiki-rendering-macros-message JAR with the changes I proposed in the PR and deploy it to your wiki. (not the most safe but quite fast if you know what you’re doing and will apply to every macro at once)
Thanks again for the report Roland
Let me know if you find any other regression!