Concerns with post template markup being ul > li

[chiilog]

What problem does this address?

• When using ul > li inside a post template, the child element's style is hit. Other elements may be hit by unintended styles.
• https://html.spec.whatwg.org/multipage/grouping-content.html#the-li-element:~:text=While%20it%20is%20conforming%20to%20include%20heading%20elements%20(e.g.%20h1)%20inside%20li%20elements%2C%20it%20likely%20does%20not%20convey%20the%20semantics%20that%20the%20author%20intended.%20A%20heading%20starts%20a%20new%20section%2C%20so%20a%20heading%20in%20a%20list%20implicitly%20splits%20the%20list%20into%20spanning%20multiple%20sections

  While it is conforming to include heading elements (e.g. h1) inside li elements, it likely does not convey the semantics that the author intended. A heading starts a new section, so a heading in a list implicitly splits the list into spanning multiple sections.

What is your proposed solution?

Change ul and li to div.

[aristath]

Hello @chiilog

I'm afraid I don't quite understand what post-template you're referring to...
Are you referring to the template for an archive of posts, where we have a list of posts? Or are you talking about a template for a single post? 🤔

[chiilog]

@aristath
Sorry for the lack of info.
I checked with the template for an archive of posts.

For example, I use the Post Content in index template.

You can see that the top of the list is nested.
The sample uses twentytwentythree, but it will be reproduced using any theme.

[ndiego]

We were able to confirm this in today's Editor Bug Scrub. The reason this occurs is because the Query Loop block uses an unordered list itself, and then any list in Post Content acts as a nested list, which receives the following CSS:

This is somewhat related to #37659. If you could change the element from a ul to perhaps a div via a selector, it would solve the issue. I imagine this would operate much like the selector in the Group block. 🤔