<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> <span class="fn">Peter Hutterer</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - Improve on-button scrolling - send both motion and scroll events for movements"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105592">bug 105592</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Summary</td>
<td>Improve on-button scrolling
</td>
<td>Improve on-button scrolling - send both motion and scroll events for movements
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>WONTFIX
</td>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEEDINFO
</td>
<td>RESOLVED
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - Improve on-button scrolling - send both motion and scroll events for movements"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105592#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - Improve on-button scrolling - send both motion and scroll events for movements"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105592">bug 105592</a>
from <span class="vcard"><a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> <span class="fn">Peter Hutterer</span></a>
</span></b>
<pre>ok, I'm going to have to say no to this one sorry. Mostly because this is a
rather experimental feature and I can see a fair number of things that can go
wrong when you interleave scroll and motion events.
Realistically, what should happen is that the compositor (using libinput) gets
both events but only forwards the scroll events, using the motion events for
cursor motion only. Alas, this cannot work because there is no association
between those two events. And not forwarding the motion events would mean the
enter/leave status is wrong in the client. That can lead to button clicks going
astray. In other words, the only way this would work is sending both events to
clients and hoping it works. AFAIK, nothing in the desktop stack is prepared
for this right now, so it may work coincidentally but certainly not by design.
Implementing this at such a low level as libinput means we have no
per-application control over the behaviour and, worse, need to implement some
toggle to allow for this behaviour. That again makes the maintenance effort a
lot greater, despite requiring the desktop environments to expose the toggles
for it.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>