https://bugs.kde.org/show_bug.cgi?id=389191
--- Comment #27 from kiv.ap...@gmail.com --- 1) Raster window scaling is done by code in KWin, isn't it? Because I remember very well that it was in KDE that this feature appeared first. Of course, you can wait for the necessary functionality to be added to XWayland, and then wait a few more years for the common applications to start supporting it (but they will most likely migrate to Wayland during this time). Or you can quickly add the ability to disable-enable raster scaling for individual applications (and develop default behavior as XWayland evolves as you want). As a result, users will be able to comfortably use KDE on Wayland today, rather than wait for years. 2) GNOME have some sort of workaround especially for Google Chrome. It is running Xwayland, but when you more its window to another screen DPI is changed. The DPI of the mouse pointer remains the same as the monitor, where the window first appeared (that is, there is every reason to assume that GNOME sends some special message to Google Chrome and it itself changes the size of the window and the scaling factor). Given that most other applications support Wayland normally and problems only with popular browsers, this workaround is in fact decisive for many people who would like to use Wayland but cannot without a browser. -- You are receiving this mail because: You are watching all bug changes.
