Version: (using KDE Devel) Installed from: Compiled sources Compiler: gcc3.2 -march=athlon-mp -msse -m3dnow -mmmx -mfpmath=sse -O3 -pipe OS: LinuxLinux Hi, look here: http://cparpart.surakware.net/public/bugs/khtml-css-001.html as you can see, the green box exceeds (on the right side) its outer box (in red). This may not be. This demo is a simplification of the bug I initially recognized on my own page, e.g.: http://www.surakware.net/projects/qpascal/specification/language/chapter01_1.xml You see, the whol text (on the right side again) exceeds the documents view. I remember a time where this bug werent there. Regards, Christian Parpart.
Server seems to be unreachable, please attach the testcases to this bug report.
Oh, I feel really very very sorry, but you just got the right time. The host is back ;) Sorry.
Is the testcase wrong or does it no browser correct? :-)
well, I tested it (initially) with Microsoft Internet Explorer 5.0/5.5 and now 6.0. All are doing it right. Whether Mozilla does it or not is unknown yet (for me). I also talked to Steffan Kulow (I believe it was he) about that problem and he also concoluded that this is more a bug in khtml than in that test case.
WinIE's behavior is incorrect -- WinIE has long implemented 'width' incorrectly. See http://www.tantek.com/CSS/Examples/boxmodelhack.html . (Note that WinIE6 implements width correctly in strict mode, as the 'width' of the content area, inside the border and padding, rather than the width of the border area.) khtml, Mozilla, Opera, and MacIE all behave correctly (last I checked, anyway).
However, I still intend that this screenshot below is rendered wrong, maybe my english isn't good enough to seek the problem direktly. Take a look at the right side (with Konqueror) and you'll surely recognize that things got cutted up: http://cparpart.surakware.net/public/bugshots/khtml-margin-padding-left-01.png Yet another bug, where I think it's located in the same region is shown on the following screenshot: http://cparpart.surakware.net/public/bugshots/khtml2.png Regards, Christian Parpart
Yup it's still a problem in HEAD
yeah, the first guy who believes me ;) and, yes, it is still in.
sorry, this is the way it should be. IE is wrong, KHTML is right.
and what about the bug screen shots I made before? I believe that this is wrong rendered anyway.