<html>
<head>
<base href="https://bugzilla.gnome.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - GtkRevealer: reveal-child should avoid changing child allocation during animation"
href="https://bugzilla.gnome.org/show_bug.cgi?id=763350#c12">Comment # 12</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - GtkRevealer: reveal-child should avoid changing child allocation during animation"
href="https://bugzilla.gnome.org/show_bug.cgi?id=763350">bug 763350</a>
from <span class="vcard"><a href="page.cgi?id=describeuser.html&login=christian%40hergert.me" title="Christian Hergert <christian@hergert.me>"> <span class="fn">Christian Hergert</span></a>
</span></b>
<pre>After digging into this a bit more, I'm starting to wonder if the issue is in
the frame clock synchronization.
In gdkwindow-wayland.c we are expecting timing information from Weston. The
timing from weston seems to be about the time of the vblank.
The timing information we get back from mutter is the time in
ClutterStage::after-page, which as far as I can tell, it not any sort of
predictable epoch to base our timings on. It just tells us when the frame was
finished drawning, not when it has been presented, or even when the vblank
occurs.</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>