[Webkit-unassigned] [Bug 25696] gtk directfb screen corruption on scrolling of webview

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri May 15 10:51:29 PDT 2009


https://bugs.webkit.org/show_bug.cgi?id=25696





------- Comment #6 from lkcl at lkcl.net  2009-05-15 10:51 PDT -------
sorry, dave, i clicked the wrong button.

also - apologies, i do not know the difference between cross-platform code and
other platform code.

all i know is that this works, and fixes a really serious show-stopper problem.
 just disabling the blitting (with the #if 0) does not fix the problem.

it is unfortunately completely impractical to go digging around in
gtk-directfb, it's _way_ too complex and time-consuming.

so - a minus review means it's unacceptable, and will thus remain unfixed.

for those people who will be searching desperately on the internet for ways to
get their code out the door, and who do not have time to go fixing up
gtk-directfb blitting bugs, or to find out what the bloody hell is going on,
try this patch: disable the blitting, and also the bit which changes the
rectangles.

i don't understand how it works, and i don't care: i just know that it works. 
if you don't add the bit which changes the rectangles, you end up with one
"flicker" (screen corruption) when you initially start scrolling a Frame, but
only when both the horizontal and vertical scrollbars are both at 0, 0 scroll
position.

thereafter, there is no further screen corruption, but even that one incident
is too much.

patch the rectangles / clipping as shown in this patch and you will get no more
flicker.


dave: paul has already mentioned that there is something wrong with the
rectangle / clipping.

thank you for mentioning about the setting in scrollview, that will help other
people.

right now, we have the solution, and there is not enough time or money to go
hunting through a complex set of code like gtk-directfb or cairo-directfb.

so if anyone else would like to follow up on this, this patch highlights where
the problems are, and at least provides a decent interim workaround.


-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



More information about the webkit-unassigned mailing list