<html>
<head>
<base href="https://bugzilla.gnome.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - wayland: Switching between fullscreen and unfullscreen using F11 in google-chrome causes gnome-shell to hang"
href="https://bugzilla.gnome.org/show_bug.cgi?id=762618#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - wayland: Switching between fullscreen and unfullscreen using F11 in google-chrome causes gnome-shell to hang"
href="https://bugzilla.gnome.org/show_bug.cgi?id=762618">bug 762618</a>
from <span class="vcard"><a href="page.cgi?id=describeuser.html&login=ofourdan%40redhat.com" title="Olivier Fourdan <ofourdan@redhat.com>"> <span class="fn">Olivier Fourdan</span></a>
</span></b>
<pre>(In reply to Jasper St. Pierre from <a href="show_bug.cgi?id=762618#c5">comment #5</a>)
<span class="quote">> Input events need to be processed with a higher priority than protocol
> events. I don't know if it will fix this bug, but it's the correct thing to
> do.</span >
Yes, you're right, I am now convinced there is nothing that can be done at the
xserver/Xwayland level here because key release events are to be processed by
the compositor first and mutter/gnome-shell is too busy dealing with wm state
changes and animations that it doesn't process the key release events.</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>