https://bugs.kde.org/show_bug.cgi?id=424434
David Edmundson <k...@davidedmundson.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |NEEDSINFO
Resolution|--- |WAITINGFORINFO
--- Comment #3 from David Edmundson <k...@davidedmundson.co.uk> ---
>I don't know what wayland is.
Upcoming replacement for X.
No windows will know their own position. Regardless of the desktop environment.
Firefox on gnome running wayland would undoubtedly hit the same issue.
---
I did look this up, the code in kwin is very deliberate about deferring the
synthetic configure events on moves.
a04e9cbc6f0547aa10ab8ce457ef0aa008d72997
Optimize away XMoveWindow() calls in the common click-and-drag case
This implements an optimization similar to one in compiz which defers
updating
the backing X window during a window move until the move is terminated.
This
helps alleviate some choppiness when using composite + vsync.
It's a trivial one line change to make but I'm relunctant to make a change that
would flood all clients with pointless configure events without hearing a
better use-case than "browser pong". Especially if they're going to have to be
broken soon anyway.
--
You are receiving this mail because:
You are watching all bug changes.
