https://bugs.kde.org/show_bug.cgi?id=503654
--- Comment #2 from Sebastian Kügler <[email protected]> --- I've discussed this with various people from both Plasma Mobile and kwin teams, here's the strategy we devised along with some background information: The general consensus is that these dialogs should not be maximized and that their sizing and placement should be similar to the sizing and placement of Kirigami (inline) dialogs. To the user, their difference it purely technical and doesn't matter. Window placement is done using the following option in kwinrc (especially the Placement = Maximizing is responsible for the jarring behaviour we want to fix): ``` [Windows] BorderlessMaximizedWindows = true Placement = Maximizing ``` This is rather a sledge hammer method. Plasma Mobile would be better of handing over the sizing policy to a kwin script that does exactly what is suitable for this platform. The dialogs we want to tackle are model QDialogs. On the Qt client API side, these are set to QDialog::setModal(true), which on the wayland platform translates to the request xdg_dialog_v1::set_modal ( https://wayland.app/protocols/xdg-dialog-v1#xdg_dialog_v1:request:set_modal ). This was implemented in Plasma 6.1 and Qt 6.8 (see https://blog.david-redondo.de/kde/wayland/qt/2024/04/04/xdg-dialog.html https://invent.kde.org/plasma/kwin/-/merge_requests/4244 https://codereview.qt-project.org/c/qt/qtwayland/+/490397 ) A script similar to the effect dimming modal dialog's parent windows can then check for modality and special case as needed. -- You are receiving this mail because: You are watching all bug changes.
