https://bugs.kde.org/show_bug.cgi?id=510591
--- Comment #20 from Vlad Zahorodnii <[email protected]> --- That part of the spec mentions that only relative motion events can be sent (without the corresponding wl_pointer.motion event). Think of video games that lock the pointer in the center of the window: the absolute position doesn't change but there are still delta values that can be sent. FWIW "The order of an absolute and relative motion event originating from the same physical motion is not guaranteed." clarifies that the compositor can send relative and absolute motion events in any order. If the compositor doesn't put relative and absolute motion events in a single frame, it's a compositor bug (but in all fairness, the protocol could be more explicit about it), the clients won't be able to say for sure whether there's only one or two motions and what the final pointer position is. -- You are receiving this mail because: You are watching all bug changes.
