Version: (using Devel) Current trunk has severe errors making KHTML unusable. I suspect this is because of qt-copy, but still I report here. I group the error descriptions in one BR, because they might have the same source (the qt snapshot): 1) the edit forms are unusable. Right now I don't see what I type. Sometimes the text appears, and disappears as I type it. The text usually reappears if I switch to another app and back, but gets messed up again if I start to type or click somewhere inside it.Sometimes it messes up the screen completely. 2) Some buttons are not rendered correctly, like the Finish button on this page, until I hover with mouse over it. See the screenshot. 3) rendering errors appear also in lists or simple lineedits.
Created attachment 23754 [details] Textedit and button errors
Created attachment 23755 [details] Lineedit error
Created attachment 23756 [details] Listbox error
The second attachment is the same as bug #158607.
This is still not completely solved, although textedit is usable (but has some rendering errors). When alien widgets were disabled, it was OK. The latest I noticed was the missing "Browse" button after the file selection line on the "Create new attachment" bugzilla page. It is there, I can click on it and it works, but it is not visible.
SVN commit 793577 by ggarand: "Fix" QPainter's complete breakage in 4.4 RC. CCBUG: 158664 M +4 -4 render_replaced.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=793577
Just for the record: I still see the wrong rendering on the query page
yeah, it's silly... all widget painting worked flawlessly for me for the whole evening yesterday, now I see artifacts again. It seems there's something triggering it Qt-wide.
*** Bug 160518 has been marked as a duplicate of this bug. ***
at the moment I can only reproduce on pages that contains at least one multiline select (iow, where the widget is a KListView). Are there pages with rendering errors that wouldn't contain one?
See bug #160518 (dup of this) for two more screenshots.
switching to a more specific bug report as some issues here are no longer reproducible. *** This bug has been marked as a duplicate of 160518 ***