<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - wayland: Make subsurface desynchronized after first parent surface frame" href="https://bugzilla.gnome.org/show_bug.cgi?id=754839#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - wayland: Make subsurface desynchronized after first parent surface frame" href="https://bugzilla.gnome.org/show_bug.cgi?id=754839">bug 754839</a> from <a href="page.cgi?id=describeuser.html&login=jadahl%40gmail.com" title="Jonas Ådahl <jadahl@gmail.com>"> Jonas Ådahl</a> <pre>Created <a href="attachment.cgi?id=311084&action=diff" name="attach_311084" title="wayland: Make subsurface desynchronized after first parent surface frame">attachment 311084</a> <a href="attachment.cgi?id=311084&action=edit" title="wayland: Make subsurface desynchronized after first parent surface frame">[details]</a> <a href='review?bug=754839&attachment=311084'>[review]</a> wayland: Make subsurface desynchronized after first parent surface frame Initially the subsurface will be in synchronized mode and we will leave it like this until the first time the parent surface has been committed. The reason for this is because the subsurface position will be applied as part of the parent surface state, and we need to synchronize the initial position with the initial frame, so that we don't accidentally draw the subsurface at the default position (0, 0) which would happen in desynchronized mode if the subsurface content is committed before the next parent surface commit.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>