<html>
<head>
<base href="https://bugzilla.gnome.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Wrong (ultra tiny/small) cursor size on HiDPI screen"
href="https://bugzilla.gnome.org/show_bug.cgi?id=744932#c142">Comment # 142</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Wrong (ultra tiny/small) cursor size on HiDPI screen"
href="https://bugzilla.gnome.org/show_bug.cgi?id=744932">bug 744932</a>
from <span class="vcard"><a href="page.cgi?id=describeuser.html&login=jadahl%40gmail.com" title="Jonas Ådahl <jadahl@gmail.com>"> <span class="fn">Jonas Ådahl</span></a>
</span></b>
<pre>(In reply to Owen Taylor from <a href="show_bug.cgi?id=744932#c141">comment #141</a>)
<span class="quote">> (In reply to Jonas Ådahl from <a href="show_bug.cgi?id=744932#c137">comment #137</a>)
>
> > Since XWayland
> > throttles buffer attaching using wl_surface_frame (it wont attach a new
> > buffer before receiving a frame callback), by waiting with replying with
> > initial frame callbacks until we have mapped, we will effectively stop
> > XWayland from attaching non-black buffers until we have already mapped and
> > drawn the window already.
>
> If the window isn't mapped, then there's no buffer attached, and we won't
> get a frame callback request from Xwayland - right?</span >
Mapped by mutter as in placed in the scene graph (yes, this term is used in
Wayland). There may be buffers attached before mutter maps it, yes. XWayland
has no idea whether mutter mapped its wl_surface or not.</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>