Version: 3.5.4 (using KDE 3.5.4, compiled sources) Compiler: Target: i586-mandriva-linux-gnu OS: Linux (i686) release 2.6.17-5mdv Konqueror renders a paragraph break <P> as a line break instead <BR> if the <P> occurs inside a list <OL><LI> The paragraph break works incorrectly on the 1st <P> but works okay on following paragraphs within the same list <LI> This was discovered while I was creating my web page and this will take you directly to the problem (Please watch-out for wrap-around): http://www.joescat.com/backup/disk_image.html#STEPS If you look at: 1. Burn a Knoppix disk. You will note that there is a line break instead of a paragraph break. You will also notice that the following paragraphs render okay as paragraphs. If you look at the source for that page, it is at approximately line 40 and 41 and looks like this: <OL><LI>Burn a <A HREF="http://www.knoppix.org/" TARGET="_blank">Knoppix</A> CDrom Disk. <P>Why Knoppi....... The same problem appears under other steps (#2...#7) which begin with <LI> and then the 1st <P> renders wrong. #2 is line 47 #3 is line 51 #4 is line 58...etc in source code Firefox and Internet Explorer were also tested but are working correctly by displaying a paragraph instead of a line break.
Confirmed, it renders different than Firefox and Internet Explorer like you say, in Opensuse 11.0 konqueror from 3.5.9 and 4.1 .
The only difference I could spot between KHTML and Firefox is the lack of a margin at the top of the <P> block. This seems to be caused by <P> tags only have margin-bottom and not a margin-top, as a result you will see a vertical space after the P block but not before. Not sure what correct behavoir is, I could imagine problems with margin-top on P elements for the case: <h1> Header </h1> <p> Text
Okay, this seems to be somewhat intentional our default stylesheet html4.css has the lines: li > p { margin-top: auto; /* margin-bottom: auto;*/ } Which exactly cancels the margin-top on P elements in LI elements. Not sure why though.
Glad to know you found the root problem. It's a start.
...just letting you know it's still a problem in KDE Version 4.6.5