Duplicate of #166, still mostly wrong. We can't remove the comment <ol> without breaking Ajax comment submission.

Sorry, didn't think to look at the closed comments. Perhaps I can take another look at the code and submit a patch that covers the Ajax bit as well.

Ok, so this patch correctly changes the ol/li to divs. All ajax functionality continues to work in Firefox including commenting, editing, and nuking. The article page is now xhtml compliant whether or not there are any comments. Just noticed the patch doesn't update the trackbacks, so be patient with me and i'll have the FINAL patch submitted in moments...

Ok, the last patch (xhtml-compliant-comments-trackbacks-with-ajax-R351.patch) should take care of both trackbacks and comments without breaking the Ajax comment post. Sorry for the multiple posts. Feel free to test at your leisure.

It does break the semantic meaning of the tags though..

That's a value statement. IMO, comments are much more than simple list items. Each comment section (or division if you will) carries a bunch of data. I think it's abusing the html concept of a list item once you add several paragraphs in a comment. Also, it's a trade-off. The software seems to place a high value on xhtml compliance (given the links in the footer). A choice must be made whether xhtml compliance is a higher priority than keeping the semantic meaning of comments equal to list items. Again, personally, I'm ok with it because I see comments as much more. To me comments are to posts as posts are to a blog, and we don't have posts as list items within a giant ordered list on the home page.

I'd very much prefer valid XHTML. I hope you find a way to achieve it.

• Removed non-existant alt="" attribute on delcious sidebar title link
• Don't display the trackback <ol> if there are no trackbacks to display
• Render a hidden dummy <li> in the comments <ol> if there are no comments to display. This element is being removed dynamically if a comment is submitted via ajax.

Closes #177