Thanks Alexandre, that seems<span></span> wise.<div><br></div><div>I&#39;ll get a review ready after 1.8.<br><br>On Monday, November 23, 2015, Alexandre Julliard &lt;<a href="mailto:julliard@winehq.org">julliard@winehq.org</a>&gt; wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Christopher Thielen &lt;<a href="javascript:;" onclick="_e(event, &#39;cvml&#39;, &#39;cthielen@gmail.com&#39;)">cthielen@gmail.com</a>&gt; writes:<br>
<br>
&gt; Fixes <a href="https://bugs.winehq.org/show_bug.cgi?id=13683" target="_blank">https://bugs.winehq.org/show_bug.cgi?id=13683</a><br>
&gt;<br>
&gt; A window may be notified with WM_CAPTURECHANGED about itself<br>
&gt; gaining mouse capture if it calls SetCapture() twice.<br>
<br>
You&#39;d need to review all places where we handle that message, I don&#39;t<br>
think we&#39;ve taken that behavior into account.<br>
<br>
Because of this risk, I&#39;m afraid it will have to wait until after code<br>
freeze.<br>
<br>
--<br>
Alexandre Julliard<br>
<a href="javascript:;" onclick="_e(event, &#39;cvml&#39;, &#39;julliard@winehq.org&#39;)">julliard@winehq.org</a><br>
</blockquote></div>