I have tested this item ✅ successfully on fe29aed

reproduced issue.
patch works as described

This fixes the issue but it pushes the background of the row outside the parent container. Not sure who did the markup for this initially but they need to understand the use of a row.

The row class should be removed from all <li> elements and properly fixed

@c-lodder do you have another idea how to fix that?

i think it was like that before.

Either replace all the row classes on <li> elements with clearfix....OR...because the grid systsem needs to be applied, don't use a list

• I have successfully tested this issue.
• I have attached Screen Shot.

I have tested this item ✅ successfully on 40305ea

I have tested this item ✅ successfully on 40305ea

Thanks for updating the markup ;)

RTC. Thanks!

I don't think we can change the markup and replace an ul with a table

@rdeutz - why?

@C-Lodder It might break templates and sites

set to needs review, because I have too look what is our policy for template changes. If someone knows it out of his head please set the milestone

6.1.7 Rendered markup

For the time being, rendered markup is not subject to our backwards
compatibility promise. We will try not to change markup in such a way that
a site might render differently, but we can't promise not to break anything
at the present time. We will work on defining ways in which we might make a
backwards compatibility promise for markup in the future, but we do not
currently have a satisfactory consensus on a workable standard.

Thanks @brianteeman

Its a tricky one as we quite often accept PR that will change the rendered markup - although usually in very subtle ways. I tend to think changing a ul to a table is not a subtle way and "could" have a bigger impact. That being said I am edging more in favour of this PR as its a clear bug and it is a relatively less used page. (I wouldnt be in favour of a change to com_content lists)

@brianteeman If replace list-striped with row-striped for ul and replace row with row-fluid for li we can keep the old markup, but this solution has a little bug marked of the red arrow. If this solution is acceptable I can commit it to PR.

That can also work. The width is not correct because someone tried to be clever and use:

.row-striped .row-fluid {
    width: 97%;
}

when it should be:

.row-striped .row-fluid {
    width: 100%;
    box-sizing: border-box;
}

If you want to submit a PR with your changes and the CSS change I've given you above, I'll be in favour of it.

@C-Lodder I don't know who and why set width: 97%;. I do not know to what side effects will lead this solution.
UPD: May be move the changing of CSS to a new PR?

@nvyush - The row-striped class is only being used on 3 HTML elements in the entire CMS, as shown in the screenshot below:

I've tested the CSS update from my previous comment and it works perfectly fine.

PR submitted: #11807

Closed as we have a PR for testing #11807