From 1d45d467d96f56ae968e9a35f5371de2cd0fbf90 Mon Sep 17 00:00:00 2001 From: Eli Zaretskii Date: Sun, 15 Sep 2024 07:55:20 +0300 Subject: [PATCH] ; * etc/PROBLEMS: Fix last change (bug#73207). (cherry picked from commit 81347c1aaf25b27e78e8beee4bc818ad2c4e1b71) --- etc/PROBLEMS | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) diff --git a/etc/PROBLEMS b/etc/PROBLEMS index 964fef3b672..d13d0d34128 100644 --- a/etc/PROBLEMS +++ b/etc/PROBLEMS @@ -3583,13 +3583,17 @@ GTK_IM_MODULE. GTK does not allow programs to warp the pointer anymore. There is nothing that can be done about this problem. -** 'frame-edges' or 'frame-geometry' does not return correct frame origin positions. - -Rather, on Wayland, they return a position not distant from 0, 0, as the -Wayland protocol is specifically engineered not to reveal this -information to clients. By the same token, `frame-monitor-workarea', -and related geometry-querying functions, cannot establish the size of -the workarea and return a placeholder result. +** 'frame-edges' and 'frame-geometry' return incorrect information + +The information returned by these and similar functions on Wayland about +frame position is incorrect. For example, 'frame-edges' can return zero +in the first 2 elements although the top-left corner of the frame is not +at pixel coordinates (0,0). This happens because the Wayland protocol +is specifically engineered not to reveal this information to clients. +For similar reasons, 'frame-monitor-workarea', +'frame-monitor-attributes', and related geometry-querying functions +cannot establish the size of the workarea, and return placeholder +results instead. ** Certain keys such as 'C-S-u' are not reported correctly. -- 2.39.2