<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [Wayland]: Totem window misplaced after a state change" href="https://bugzilla.gnome.org/show_bug.cgi?id=771915#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [Wayland]: Totem window misplaced after a state change" href="https://bugzilla.gnome.org/show_bug.cgi?id=771915">bug 771915</a> from <a href="page.cgi?id=describeuser.html&login=bjorn.lie%40gmail.com" title="Bjørn Lie <bjorn.lie@gmail.com>"> Bjørn Lie</a> <pre>(In reply to Olivier Fourdan from <a href="show_bug.cgi?id=771915#c6">comment #6</a>) > Comment on <a href="attachment.cgi?id=336192&action=diff" name="attach_336192" title="[PATCH] gtkwindow: Update on state event only for unrealized">attachment 336192</a> <a href="attachment.cgi?id=336192&action=edit" title="[PATCH] gtkwindow: Update on state event only for unrealized">[details]</a> <a href='review?bug=771915&attachment=336192'>[review]</a> [review] > [PATCH] gtkwindow: Update on state event only for unrealized > > Just to make it clear, this patch is a no-go, as it's in effect a revert of > the fix for <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Epiphany application mode on Wayland broken with WebKit 2.13.92" href="show_bug.cgi?id=771561">bug 771561</a> which is a (more) serious issue. > > The goal here is to fix this issue without reintroducing <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Epiphany application mode on Wayland broken with WebKit 2.13.92" href="show_bug.cgi?id=771561">bug 771561</a> again. Sure, but with my current "patch" set (I noticed that I have a couple of mutter patches in plus), I can not reproduce <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Epiphany application mode on Wayland broken with WebKit 2.13.92" href="show_bug.cgi?id=771561">bug 771561</a> anymore.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>