<html>
<head>
<base href="https://bugzilla.gnome.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - GtkWindow reacts on maximize action even if it is fixed-width"
href="https://bugzilla.gnome.org/show_bug.cgi?id=757530#c11">Comment # 11</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - GtkWindow reacts on maximize action even if it is fixed-width"
href="https://bugzilla.gnome.org/show_bug.cgi?id=757530">bug 757530</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 Jonas Ã…dahl from <a href="show_bug.cgi?id=757530#c9">comment #9</a>)
<span class="quote">> (In reply to Matthias Clasen from <a href="show_bug.cgi?id=757530#c7">comment #7</a>)
> > Review of <span class=""><a href="attachment.cgi?id=314814&action=diff" name="attach_314814" title="[Patch 2/3] wayland: apply maximized state only when possible">attachment 314814</a> <a href="attachment.cgi?id=314814&action=edit" title="[Patch 2/3] wayland: apply maximized state only when possible">[details]</a></span> <a href='review?bug=757530&attachment=314814'>[review]</a> [review] [review]:
> >
> > ::: gdk/wayland/gdkwindow-wayland.c
> > @@ +1033,1 @@
> > }
> >
> > Is it ok to not ack configure ?
>
> Yes. According to the current spec it is Ok to drop all configure requests
> except the last one, but since there might already be a configure request on
> the wire when the client drops all but the last and acks that, I don't see
> how the server can disallow that ack anyway.</span >
Beside, if we ack the request without applying the changes to the state/size,
the Wayland compositor reckons the configure was successful and will move the
window to the top left corner (as it would if it was actually maximized), which
is not what we want here as we didn't allow for maximization.
So I reckon we shouldn't ack the request if we didn't apply it.
The spec reads:
When a configure event is received, if a client commits the
surface in response to the configure event, then the client
must make an ack_configure request sometime before the commit
request, passing along the serial of the configure event.
For instance, the compositor might use this information to move
a surface to the top left only when the client has drawn itself
for the maximized or fullscreen state.
If the client receives multiple configure events before it
can respond to one, it only has to ack the last configure event.
A client is not required to commit immediately after sending
an ack_configure request - it may even ack_configure several times
before its next surface commit.
The compositor expects that the most recently received
ack_configure request at the time of a commit indicates which
configure event the client is responding to.</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>