<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#c1">Comment # 1</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=jadahl%40gmail.com" title="Jonas Ådahl <jadahl@gmail.com>"> <span class="fn">Jonas Ådahl</span></a>
</span></b>
<pre>(In reply to Olivier Fourdan from <a href="show_bug.cgi?id=762618#c0">comment #0</a>)
<span class="quote">> But this doesn;t seem to be coming from an actual state change because
> breaking on xdg_surface_set_fullscreen()/xdg_surface_unset_fullscreen() in gdb
> shows these are not triggered while the Javascript routines are called
> continuously.</span >
Isn't google-chrome an X11 application? So it wouldn't go via xdg_surface_*
functions. I don't know how X11 applications fullscreen themself, but there is
the meta_window_make_fullscreen and friends that might be helpful.
Have you only seen it on google-chrome or other clients as well?</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>