| Summary: | Incorrect client geometry reported via KWin scripting API for gtk4-demo running on XWayland | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Michael Weghorn <m.weghorn> |
| Component: | scripting | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | m.weghorn |
| Priority: | NOR | ||
| Version First Reported In: | 6.0.3 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Sample KWin script to print client geometry of all windows
Screenshot showing current result on Fedora Rawhide |
||
|
Description
Michael Weghorn
2024-04-03 09:10:08 UTC
Created attachment 168083 [details]
Screenshot showing current result on Fedora Rawhide
After discussion on a similar ticket for GNOME Shell (see https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7559 ), I think the returned values are fine and my expectations were wrong. -> Closing as INVALID > This is e.g. relevant for accessibility tools. (E.g. a magnifier that > automatically follows the position of the text caret would might then result > in the wrong part of the screen being in view.) > I ran into this while implementing support in Accerciser to retrieve window > coordinates from KWin on Wayland. This works now with an updated MR taking into account the discussion from above-mentioned gnome-shell ticket: https://gitlab.gnome.org/GNOME/accerciser/-/merge_requests/57 |