procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

; * etc/PROBLEMS: Fix last change (bug#73207).

Browse source
This commit is contained in:
Eli Zaretskii 2024-09-15 07:55:20 +03:00
parent a82b7f3e82
commit 81347c1aaf
1 changed files with 10 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
etc/PROBLEMS
View file

@ -3583,13 +3583,17 @@ GTK_IM_MODULE.
GTK does not allow programs to warp the pointer anymore. There is GTK does not allow programs to warp the pointer anymore. There is
nothing that can be done about this problem. nothing that can be done about this problem.
** 'frame-edges' or 'frame-geometry' does not return correct frame origin positions. ** 'frame-edges' and 'frame-geometry' return incorrect information
Rather, on Wayland, they return a position not distant from 0, 0, as the The information returned by these and similar functions on Wayland about
Wayland protocol is specifically engineered not to reveal this frame position is incorrect. For example, 'frame-edges' can return zero
information to clients. By the same token, `frame-monitor-workarea', in the first 2 elements although the top-left corner of the frame is not
and related geometry-querying functions, cannot establish the size of at pixel coordinates (0,0). This happens because the Wayland protocol
the workarea and return a placeholder result. 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. ** Certain keys such as 'C-S-u' are not reported correctly.