<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - modesetting driver plus DRI3 causes extremely slow scrolling with WebKitGTK+ in accelerated compositing mode" href="https://bugs.freedesktop.org/show_bug.cgi?id=85064#c41">Comment # 41</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - modesetting driver plus DRI3 causes extremely slow scrolling with WebKitGTK+ in accelerated compositing mode" href="https://bugs.freedesktop.org/show_bug.cgi?id=85064">bug 85064</a> from <a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> Michel Dänzer</a> <pre>(In reply to Carlos Garcia Campos from <a href="show_bug.cgi?id=85064#c40">comment #40</a>) > Yes, this is because we use the screen width + 1 to position our window > offscreen: > > WidthOfScreen(screen) + 1, 0, 1, 1, FWIW, WidthOfScreen is bad anyway because that's just how wide the screen happened to be when the X11 display connection was established. The screen can be widened after that via the RandR extension, in which case the window would become visible. > and it turns out that simply using -1, -1 as coordinates fixes the problem. Weird, not sure why that avoids the problem; maybe there's an off-by-one bug somewhere which causes the window to be incorrectly considered on-screen. I wouldn't recommend relying on that. Also, again I'm not sure that negative coordinates can never be visible. So, why does this code use a window instead of a pixmap? Assuming a window is really the only possibility, (why) can't it set the swap interval to 0 via one of the GLX extensions for this, to prevent SwapBuffers operations from getting throttled?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>