‘which I have removed. It seems to work now.’

Will you ever listen? Regardless of what you do with the CSS, your HTML markups are still broken. The validator will still tell you that there are stray <li> tags in line 230 and 231, and your layout will still be shown as messed up in most browsers after those lines.

Stop being obtuse.

list-style:none

which I have removed. It seems to work now.

Stop being obtuse – you are simply digging yourself into a hole as we speak.

This is what I see with this test:

My browser displays

A

B

CSS is screwed up somewhere. HTML is correct.

Chrome browser reports:
media=”all”
.widefat * {
word-wrap: break-word;
}
edit-comments.phpmedia=”all”
li, dd {
margin-bottom: 6px;
}
user agent stylesheetli {
display: list-item;
text-align: -webkit-match-parent;
}
Inherited from ul
edit-comments.phpmedia=”all”
.widefat td p, .widefat td ol, .widefat td ul {
font-size: 12px;
}
edit-comments.phpmedia=”all”
.widefat p, .widefat ol, .widefat ul {
color: #333;
}
edit-comments.phpmedia=”all”
ul {
list-style: none;
}
user agent stylesheetul, menu, dir {
list-style-type: disc;
}
Inherited from td.comment.column-comment
edit-comments.phpmedia=”all”
.widefat td {
color: #555;
}
edit-comments.phpmedia=”all”
.widefat td {
font-size: 12px;
}
edit-comments.phpmedia=”all”
td, textarea {
line-height: inherit;
}
edit-comments.phpmedia=”all”
td, textarea, input, select {
font-family: inherit;
font-size: inherit;
font-weight: inherit;
}
Inherited from table.widefat.fixed.comments
edit-comments.phpmedia=”all”
.widefat {
border-spacing: 0;
}
user agent stylesheettable {
border-collapse: separate;
border-spacing: 2px;
border-color: gray;
}
Inherited from div#wpbody
edit-comments.phpmedia=”all”
body, #wpbody, .form-table .pre, .ui-autocomplete li a {
color: #333;
}
Inherited from body.wp-admin.js.edit-comments-php.admin-bar.branch-3-4.version-3-4-2.admin-color-fresh.locale-en-us.no-customize-support
edit-comments.phpmedia=”all”
body, #wpbody, .form-table .pre, .ui-autocomplete li a {
color: #333;
}
edit-comments.phpmedia=”all”
body {
font-family: sans-serif;
font-size: 12px;
line-height: 1.4em;
}

That’s what I call bloat. “list-style: none” could be helpful…

‘Somewhere between TinyMCE, WordPress and my browser they mess up. By leaving off the ul tags, my browser shows them correctly.’

Then stop using lists.

As I have already mentioned, each comment here is formatted as a list item (i.e. <li>…</li>) inside an ordered list (<ol>…</ol>). By leaving out the enclosing unordered list tags(<ul>…</ul>), the list items become their own individual “comments”.

Also, list items are not supposed to be present outside <ol>…</ol> or <ul>…</ul>. That’s an incorrect use of the <li>…</li> tags.

W3C Markup Validation Service:

‘Line 231, Column 4: document type does not allow element “li” here; missing one of “ul”, “ol”, “menu”, “dir” start-tag’

What good is a standard for if you don’t follow it?

in posts. Comments are the problem for me. Using

causes the
• s to disappear in my comments. It’s a CSS thing or an WP thing. I don’t know which. Haven’t looked into it.

See? I included a ul tag and wp matched it with a /ul tag and then matched the li with a /li and /ul and still messed it up. No li or /li tags in the result.

It’s _not_ a browser issue. Your site is generating bad markup. The LI thing is just the one that’s screwing up layout.

http://goo.gl/avTdN

And it’s Firefox 14.0.1, if you must know.

If it helps, WordPress is adding a closing LineItem (LI) tag outside a DIV. If you can’t fix it, it might help if you used the OL or UL tags to contain your lists, instead of just using LI to define items.