Some updates to Investigating Konqueror Bugs: www.konqueror.org/investigatebug/

["Gérard Talbot"]

Updates, proposals to make to

Investigating Konqueror Bugs
http://www.konqueror.org/investigatebug/

In that webpage, people should be invited to

- clearly identify the rendering engine: is it webkit or KHTML? That's
useful info that should be in their bug report.
- identify the webpage (url) on which the problem occurs; in case of crash
reporting, people often paste a backtrace but not the webpage url!
- identify the rendering mode (View/Show Document info ...
Ctrl+I/Rendering mode) . Btw, "Strict" is not very good: "Web Standards
compliance" would be best.


An "Investigating Konqueror Bugs" webpage should invite people to file a
bug report on only 1 single webpage and one single issue. One bug report,
one issue only.

In the bug description and report, they should keep as formal as possible
at all times and as factual as possible at all times. Rants, advocacy and
negativity, anger and impatience are not helpful to anyone and will not
help fix a bug.


Also, claiming that other browsers do this or do that may be, in some
cases, useful but, strictly speaking, it does not help in any way a bug
filed on Konqueror (KHTML or webkit rendering engine).

By itself and of itself, the fact that other browsers do this or do that
does not necessarly mean anything. Those other browsers may have bugs,
spec violations to begin with and they do have bugs, flaws, spec
violations too.

If they think that the fact that other browsers succeed in doing
something, then they should at least identify browser versions. To be told
that "IE succeeds in rendering this page" means absolutely nothing as IE6,
IE7, IE8, IE9 and IE10PP2 are available and in use on the web; on top of
that, IE8+ all have multiple rendering compatibility modes, and even a
backward-compatible "quirks"/bugward rendering mode!


In Investigating Konqueror Bugs
http://www.konqueror.org/investigatebug/
people should be told that anything that can help reproduce, clarify and
"corner" the real issue involved is going to be helpful. A reduced
testcase often does that.


In Investigating Konqueror Bugs
http://www.konqueror.org/investigatebug/
we can read:

"
This page is about bugs in the web browser only. For bugs in the file
manager, or about any other KDE application, jump directly to the generic
How to report a bug in KDE ( http://bugs.kde.org/Reporting.html ).
"
but
http://bugs.kde.org/Reporting.html
is 404 NOT FOUND !

regards, Gérard
-- 
Konqueror Implementation Report of CSS 2.1 test suite (RC6): 9418 testcases
http://www.gtalbot.org/BrowserBugsSection/Konqueror4Bugs/Konq-IR-CSS21TestSuite.html
49 Bugs in Konqueror 4.7
http://www.gtalbot.org/BrowserBugsSection/Konqueror4Bugs/
Contributions to the CSS 2.1 test suite
http://www.gtalbot.org/BrowserBugsSection/css21testsuite/
CSS 2.1 Test suite RC6, March 23rd 2011
http://test.csswg.org/suites/css2.1/20110323/html4/toc.html