When wrapping a long line of text, Konqueror adds a space to the beginning of each displayed line of text after the first displayed line. For instance, in the Description in bug 50000, the paragraph after the greeting is one long line. In my browser, with a particular width, this is displayed as (using U+0180 to represent space): when I try to ... ƀenter correct ... ƀ(the wrong one) ... This happens only with KHTML and not with WebKit. (To reproduce, after switching browser engine in Configure/General, it's necessary to refresh the page.)
I see that as a feature. When marking the text and copying it, the space that "separates" the lines is not lost.
Actually, this is a CSS feature, and this site has adopted it. It does not happen everywhere.
Is it a bug in WebKit, then, that it doesn't conform to CSS?
The CSS attribute to look for is "white-space: pre-wrap". The W3C CSS TR says "If a space (U+0020) at the beginning of a line has 'white-space' set to 'normal', 'nowrap', or 'pre-line', it is removed." In other words, it is not removed for 'pre-wrap'. The line break, however, should not be before the space, but after it. Again quoting the CSS TR: "However, for 'pre-wrap', a line breaking opportunity exists at the end of the [spaces] sequence." So it is wrong in KHTML. http://www.w3.org/TR/CSS21/text.html#propdef-white-space
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!
The bug is still present in Konqueror 5.0.97. However, I no longer use KHTML (in fact, I'm surprised to find it's still supported).
Thanks for the update!
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