CSS 2.1 & 3 Support in KHTML webpage needs to be updated ======================================================== Hello all, I spent quite a bit of time yesterday updating Interactive CSS 3 Background tests http://www.gtalbot.org/DHTMLSection/InteractiveCSS3BackgroundTests.html and found that http://www.konqueror.org/css/ was, in my opinion, quite outdated. The website http://www.css3.info/preview/ suggested that several CSS 3 properties were supported (albeit with the -khtml- prefix). I have sent today an email to Allan Sandfeld. Regards, Gérard
I think large portions of that are outdated. ;)
Suggestions: 1- A "yes" cell should be white on green background-color; A "no" cell should be white on red background-color. 2- "partial" or "incomplete" should be a possible choice. A "partial" or "incomplete" cell should be black on yellow background-color. It's possible to use light green and light red background-colors and to use black color for text like at http://www.opera.com/docs/specs/presto211/css/index.dml http://msdn.microsoft.com/en-us/library/cc351024(VS.85).aspx#selectors http://www.webdevout.net/browser-support-css#css2units For darker green and darker red background-colors: http://www.quirksmode.org/css/contents.html#t10 3- Many (if not, all!) CSS support and compliance documentation charts are presented by section of specification instead of alphabetical order of property names. eg http://www.webdevout.net/browser-support-css https://developer.mozilla.org/En/Mozilla_CSS_support_chart Regards, Gérard
I know this isn't a Konqueror bug, however it isn't a documentation bug either, well it kind of is, but the documentation project doesn't have access in order to fix anything and I think it would be better for the Konqueror devs to look at getting it fixed. Maybe one of the Konqueror devs can forward this on to the correct person who can update their website?
Richard, I agree with you that this bug may not be a Konqueror bug nor a documentation bug. If you tell me how (with correct application field, with correct product field, with correct component field) to file this bug, then I will resolve this bug 176306 and create a new bug report to report it accordingly. If you visit http://www.konqueror.org/css/ you'll see at the bottom of the page that such page is "Maintained by konqueror.org Webmaster" <webmaster konqueror org> so maybe we should contact such webmaster (add <webmaster konqueror org> to CC list?). +CC Allan Sandfeld regards, Gérard
CSS 2.1 Conformance Test suite (Release Candidate 5) built on January 11th 2011: http://test.csswg.org/suites/css2.1/20110111/ (9590 testcases) CSS 2.1 Test Suite (Release Candidate 5) test harness: http://test.csswg.org/harness/ Konqueror 4.5.5 implementation report of CSS 2.1 test suite (Release Candidate 5): 3300 testcases done so far. Implementation report for the first 3300 testcases has been edited. Konqueror 4.5.5 report of CSS 2.1 test suite (Release Candidate 5) of first 3300 testcases: http://www.gtalbot.org/BrowserBugsSection/Konqueror4Bugs/Konq-IR-CSS21TestSuite.html There are so far at least 13 testcases - clearly identified - which will cause application crash or CPU hang (infinite reflow: the CPU - %tage activity - gets maximized and remains maximized: so the application becomes unresponsive) 4 generated content testcases causing CPU hang (infinite reflow) bugs ===================================================================== after-content-display-011 before-after-display-types-001 before-after-table-parts-001 before-content-display-011 9 :first-letter testcases causing application crash =================================================== before-first-letter-selector-001 first-letter-dynamic-001 (causes crash or its reftest causes crash) first-letter-quote-002 (its reftest causes crash) first-letter-quote-003 (its reftest causes crash) first-letter-quote-004 (its reftest causes crash) first-letter-quote-005 (its reftest causes crash) first-letter-quote-006 (its reftest causes crash) first-letter-selector-005 first-letter-selector-009 (causes crash when leaving page) regards, Gérard
CSS 2.1 Conformance Test suite (Release Candidate 6) built on March 23rd 2011: http://test.csswg.org/suites/css2.1/20110323/ (9418 testcases) CSS 2.1 Test Suite (nightly unstable) test harness on 9503 testcases: http://test.csswg.org/harness/ Konqueror 4.6.3 implementation report of CSS 2.1 test suite (Release Candidate 6): 7000 testcases done so far and is available. Konqueror 4.6.3 report of CSS 2.1 test suite (Release Candidate 6) of first 7000 testcases: http://www.gtalbot.org/BrowserBugsSection/Konqueror4Bugs/Konq-IR-CSS21TestSuite.html regards, Gérard
I believe Product for this bug should be www.kde.org and then Component should be general Gérard
CSS 2.1 Conformance Test suite (Release Candidate 6) built on March 23rd 2011: http://test.csswg.org/suites/css2.1/20110323/ (9369 testcases) CSS 2.1 Test Suite (nightly unstable) test harness on 9503 testcases: http://test.csswg.org/harness/ Konqueror 4.6.4 implementation report of CSS 2.1 test suite (Release Candidate 6): 7971 PASSED testcases 1341 FAILED testcases 7971 / 9312 = 85.60% ---------- 44 testcases are considered INVALID; if I apply stricter rules, then there are more than 44 invalid testcases. 9 testcases UNKNOWN because I do not have a color printer and Konqueror does not have a print preview feature (Folks, please vote for bug 258634 ) 2 testcases: hangs or refuses to print: I need someone else to confirm + verify this. 2 testcases UNKNOWN because of several characters not displayed possibly due to font availability; I need someone else to confirm + verify this. Konqueror 4.6.4 report of CSS 2.1 test suite (Release Candidate 6) of all 9369 testcases: http://www.gtalbot.org/BrowserBugsSection/Konqueror4Bugs/Konq-IR-CSS21TestSuite.html regards, Gérard
Dear user, KHTML (and KJS) was a long time more or less unmaintained and got removed in KF6. Please migrate to use a QWebEngine based HTML component. We will do no further fixes or improvements to the KF5 branches of these components beside important security fixes. For security issues, please see: https://kde.org/info/security/ Sorry that we did not fix this issue during the life-time of KHTML. Greetings Christoph Cullmann