<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - It is impossible to screenshot a user selected window."
href="https://bugs.freedesktop.org/show_bug.cgi?id=99635#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - It is impossible to screenshot a user selected window."
href="https://bugs.freedesktop.org/show_bug.cgi?id=99635">bug 99635</a>
from <span class="vcard"><a class="email" href="mailto:daniel@fooishbar.org" title="Daniel Stone <daniel@fooishbar.org>"> <span class="fn">Daniel Stone</span></a>
</span></b>
<pre>(In reply to naelstrof from <a href="show_bug.cgi?id=99635#c5">comment #5</a>)
<span class="quote">> Oh I want to clarify: Input grabbing is completely unnecessary. The wayland
> port of slop just covers the whole screen as a fullscreen application which
> works great.
> Slop just needs a way to know where windows are in relation to the pointer.
> In X11 slop can simply ask for all surfaces intersecting with the pointer.</span >
... that doesn't work for windows which are currently occluded. For that
reason, Chrome's screencasting offers a grid view of all current top-level
windows, with previews. This to me seems a far better approach than
xwininfo-style get-window-under-pointer.
<span class="quote">> Maybe the extension could be similar, where compositors could be pretty
> clever with it and make it return actual windows when hovering over a window
> list on a task bar, or on a mini-window inside of a workspace.</span >
Sure, but then a malicious app could use that to just get all windows all the
time, which wouldn't be fun. I'd much rather see something like the Flatpak
document portal:
<a href="http://flatpak.org/xdg-desktop-portal/portal-docs.html#gdbus-org.freedesktop.portal.FileChooser">http://flatpak.org/xdg-desktop-portal/portal-docs.html#gdbus-org.freedesktop.portal.FileChooser</a>
The compositor could then present a list of windows to select from (in
whichever manner it feels is appropriate), and either provide a screenshot or
cast immediately. This makes the intent unambiguous, sidestepping the security
issue, and also avoids the indirection in your suggestion.
tl;dr the request should be 'I would like to shot/cast a window'; let the
compositor sort the rest</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>