<html>
<head>
<base href="https://bugzilla.gnome.org/" />
</head>
<body><span class="vcard"><a href="page.cgi?id=describeuser.html&login=carlosg%40gnome.org" title="Carlos Garnacho <carlosg@gnome.org>"> <span class="fn">Carlos Garnacho</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - wayland: connection flooded when dragging"
href="https://bugzilla.gnome.org/show_bug.cgi?id=763298">bug 763298</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;">Attachment #323608 is obsolete</td>
<td>
</td>
<td>1
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - wayland: connection flooded when dragging"
href="https://bugzilla.gnome.org/show_bug.cgi?id=763298#c12">Comment # 12</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - wayland: connection flooded when dragging"
href="https://bugzilla.gnome.org/show_bug.cgi?id=763298">bug 763298</a>
from <span class="vcard"><a href="page.cgi?id=describeuser.html&login=carlosg%40gnome.org" title="Carlos Garnacho <carlosg@gnome.org>"> <span class="fn">Carlos Garnacho</span></a>
</span></b>
<pre>Created <span class=""><a href="attachment.cgi?id=323875&action=diff" name="attach_323875" title="gdkdnd: Add private means to commit the drag status">attachment 323875</a> <a href="attachment.cgi?id=323875&action=edit" title="gdkdnd: Add private means to commit the drag status">[details]</a></span> <a href='review?bug=763298&attachment=323875'>[review]</a>
gdkdnd: Add private means to commit the drag status
The way gdk_drag_status() may be called multiple times during the
processing of GDK_DRAG_MOTION events throughout the widget hierarchy
brings some superfluous messaging going in, esp. when it's the last
request the one we want to honor, yet we emit messaging requests on
all.
This is barely appreciable in the X11 backend, but due to the design
of the wayland protocol, quick series of changes like this it have
some self-amplificating consequences which may end up flooding the
connection.
We can delegate this to a late "commit" call, performed within GDK
event management. This way gdk_drag_status() calls may be cached
and only result in windowing messaging once per GDK_DRAG_MOTION
event. Emitting the final status will also avoid spurious action
changes on the compositor and the other peer.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>