<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Implement wl_probe, or something similar"
href="https://bugs.freedesktop.org/show_bug.cgi?id=75382#c9">Comment # 9</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Implement wl_probe, or something similar"
href="https://bugs.freedesktop.org/show_bug.cgi?id=75382">bug 75382</a>
from <span class="vcard"><a class="email" href="mailto:x414e54@linux.com" title="x414e54@linux.com">x414e54@linux.com</a>
</span></b>
<pre>(In reply to x414e54 from <a href="show_bug.cgi?id=75382#c8">comment #8</a>)
<span class="quote">> >
> > It can also expand its buffer size while keeping the same input region and
> > buffer content making the expansion transparent, until it receives a
> > "wl_surface.enter", and then calculate its position. That doesn't mean
> > wl_surface.enter is the wrong thing to do.
>
> This would not work if there was only one display or they were not stitched
> together.
> But it is a fair point.</span >
If you would like an example of one of the reasons why I am worried about this
please see how chrome is working on XWayland here: <a href="https://youtu.be/PTu7-hBwZ1o">https://youtu.be/PTu7-hBwZ1o</a></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>