List items can't have bold text (flex box problem)

Hi, I love the list item block, and flex box on li elements really does that job.

A lot of users, myself included, like to have some text bold/strong for reading/marketing purposes. And yes, Flexbox treats this as an element of course so you get a strange look once an element needs a new rule. see screenshot.

Schermafbeelding 2023-01-04 om 15.14.27

This is the code:
Schermafbeelding 2023-01-04 om 15.14.37

Adding flex-wrap: wrap; makes it better, but than the problem arises that the text will go under the list-item. see screenshot.
Schermafbeelding 2023-01-04 om 15.16.48

I would expect to happen that I can add elements inside a list item without effecting the layout.

Maybe there is a way out of here with CSS, but it would be great if Cwicly offered this option.

Environment info

Cwicly Versie

Hi there @webmaat,

This is unusual as the List block (with icons active), does have the necessary added to it to ensure this doesn’t happen.
Have you added any particular properties to the block?
Could I possibly have a screenshot of the whole block markup (with the div)?

Thanks in advance.

Hi Louis,

No, only used the list block and filled it in with text.
Also normal list item…

Here you can see the DOM yourself: Webmaat
(mind that there’s still a mixed content problem with the Cwicly Stylesheets for which I e-mailed you 2 days ago. in firefox you have to bypass this to view the right CSS rendering…

Hi @webmaat,

This is what I’m getting (default styles added by Cwicly):

Sorry to hear that you’ve had no reply.
You’ll have to remind me on this one as I cannot find a reference to it.

I’m sorry, I wasn’t clear. It happens when you make screen smaller. So on mobile you get to see the problem. it also occurs when I relative style it with span. So the problem is flex box on li element.

I had a reply on my list of things this morning…but I forgot to have this issue also on the list. I’ll get back to Johnny about it.

Hi @webmaat,

I can confirm the issue with the List block when icons are active. As you rightly described, the display: flex; property makes it very difficult to have the items wrap properly.

In this case, we will be adding an outer <span> element inside the <li> element to contain the inner children and resolve the issue.

An option will also be provided in case you don’t want to have this <span> element added.

Thanks for the precise report, much appreciated.


Thanks Louis for taking these ‘bugs’ serious.

1 Like

Hi @webmaat,

This should be fixed in with a post save or regenerating the HTML.

If you still experience trouble with this, please let me know by replying to this thread.


1 Like

Hi @Louis
It seems that the problem has been resolved in the frontend, but it still persists in the backend. I have a list with icons and some parts of the list items are bolded. The frontend looks fine, but the backend appears as follows:

I am aware of the “Remove List Container” option, which is disabled for me to include a <span> element inside a <li> . However, it seems that the <span> element is added only in the frontend, not in the backend. At least, that’s the case for me."

I confirm what @krievinshj wrote: span is not added inside the editor.

By the way, is the use of flex really appropriate here?
I wish this block was closer to standard HTML ul/li tags so that we could use the same CSS for styling.
(I guess the SVG icon adds complexity to the classic list, though…)

Bump @Louis,

This is very annoying and makes me feel unconfortable with clients.

PS: Other bugs are WRONGLY marked as FIXED on this forum and I have the feeling they are more and more being forgotten :wink:

@yankiara Which other bugs?


I reported this (critical) one more than 3 months ago:

This one is minor:

BUMP :pray:

Still not fixed backend, new clients complaining…


Thanks so much for bumping this thread.

A fix for this is not easily achieved without reviewing the way Cwicly lists are rendered on the frontend as we don’t fully control the RichText controller.

An in depth review of the Cwicly List block is planned.
While we appreciate this is an inconvenience for users on the backend, the flexibility provided by the Cwicly List block is something we have to consider before reworking it.

Best regards,

Thanks for the update :slight_smile:

But do you mean we shouldn’t use it meanwhile?
Any potential backward compatibility issues?


Sorry if I didn’t make that clear: a rework with functional changes made to the List block will be backwards compatible.

Best regards,

We have used some styles to override the default list block styles for one of our sites to address this - we are happy to provide these if it helps.