Version: (using KDE 4.3.3) Installed from: Ubuntu Packages I have found a CSS difference between Firefox/IE and Konqueror. Go to the following page: http://www.webisco.de/demo The left blue tree navigation has an offset of 10 pixels although this is not defined in the CSS file. Firefox and IE align the div correctly at the left border aligned to the other div at the top. Do you need a smaller example page or is this demo page okay for you to reproduce the CSS-bug?
> I have found a CSS difference between Firefox/IE and Konqueror. Go to the > following page: > > http://www.webisco.de/demo > > The left blue tree navigation has an offset of 10 pixels I notice also the 10 pixels offset while using Konqueror 4.6.4. > although this is not > defined in the CSS file. Firefox and IE align the div correctly at the left > border aligned to the other div at the top. I confirm your finding (horizontal alignment) with Firefox 5.0. This may not be a CSS bug; it's too soon at this point to say. > Do you need a smaller example page or is this demo page okay for you to > reproduce the CSS-bug? A reduced, minimized testcase is *always* better, for many reasons. " Unfortunately due to the large number of bug reports received, and the large amount of time that it takes developers to identify issues, reports which do not include a testcase or are not described in reproduceable steps will get a low priority of fixing. (...) HTML/CSS problem Your bug is related to HTML and/or CSS. You need to know a bit HTML and follow these steps to build a test case: Save the relevant page or frame on your disk. Load the page from your disk and see if the problem is still there. Only if it's necessary to reproduce the bug: save framesets, images etc. Throw out anything that has nothing to do with the bug, i.e. delete some stuff, reload to check if the problem is still there, delete more stuff. Do this until you found the exact cause of the problem. The HTML file should not have more than 20 lines at the end. The important part is: the page should be as short as possible to be able to still reproduce the bug. The shorter it is, the sooner it will get fixed! (...) " Investigating Konqueror Bugs http://www.konqueror.org/investigatebug/ Also, if you suspect the bug is CSS related, then the testcase should demonstrate a CSS issue or problem with javascript support disabled. Right now, the http://www.webisco.de/demo has a lot of javascript involved, many CSS declarations in http://www.webisco.de/demo/webisco.css , invalid HTML code Gérard
I am sorry, but the HTML code of the page is validating with w3c's validator: http://validator.w3.org/check?uri=http%3A%2F%2Fwww.webisco.de%2Fdemo It has not invalid HTML. You can also disable JavaScript and the 10 pixels are printed there. I thought a valid DOM is an easy testcase for khtml. Please don't bother on the given example. You could have asked me instead to minify the HTML to point out the mistake better. If I weren't cooperative I never would have reported the bug. But I don't want to invest more time in that issue until someone takes care of the bug. I hope you can understand this. Andreas
> I am sorry, but the HTML code of the page is validating with w3c's validator: > > http://validator.w3.org/check?uri=http%3A%2F%2Fwww.webisco.de%2Fdemo It is valid now. When I visited that page, I swear it had what I wrote: a lot of javascript involved, many CSS declarations and invalid HTML code. The http://www.webisco.de/demo/webisco.css has - today - 1251 lines of code and 25411 bytes (that's 25 Kilo-bytes) long! That is not reduced. The http://www.webisco.de/demo/ has - today - 15 lines long but 28271 characters/bytes (that's 28 Kilo-bytes) long! That is not reduced. If the javascript (http://www.webisco.de/23/1/webisco.min.js has - today - 2602 bytes minified - that is with blank spaces removed and with one-letter js variables) is not involved, then why include it? Why not remove it? > valid DOM is an easy testcase for khtml The http://www.webisco.de/demo DOM tree could be well-formed but it could still be wide and deep: this is the case here. The markup code uses 11 tables, including nested tables, constrained tables and constrained table cells. It's possible that your nested tables have overconstrained table cells in which case the HTML4 does not provide any rule, any error handling mechanisms. This can be the case for CSS 2.1, even in table-layout fixed algorithm. But we can't be sure of anything right now. Everything would be a lot more clear, more certain with a reduced test case. Also, presentational attributes are sometimes rendered differently with transitional DTD; a doctype pointing to strict DTD is always better. > You could have asked me instead to > minify the HTML to point out the mistake better. Haven't I? This is comment #1: { > Do you need a smaller example page or is this demo page okay for you to > reproduce the CSS-bug? A reduced, minimized testcase is *always* better, for many reasons. (...) } and then I even quoted "Investigating Konqueror Bugs" document. > I don't want to invest more time in that issue until someone takes care > of the bug. Andreas, what if a developer is thinking: "I don't want to invest more time into bug reports that don't include a reduced testcase"? Reducing testcases: why make reduced testcases https://developer.mozilla.org/en/Reducing_testcases#Why_make_reduced_testcases.3F The WebKit Open Source Project: Test Case Reduction: Why is it needed? http://www.webkit.org/quality/reduction.html Gérard
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!