https://bugs.documentfoundation.org/show_bug.cgi?id=156263
--- Comment #38 from [email protected] --- First, thanks for fixing this issue! It drove me nuts for some days... I can confirm 25.8.2 works on linux+wayland (nixos). However, little nitpicking: I'm not sure if the actual reason for this issue is solved. I noted 2 behaviours, one was the "UI locking", the second one is about the window state itself. Opening the validation popup creates a modal (as expected). It's not shown as a separate window by my window manager (plasma6/kwin), alt+tab shows the modal replaced the main window since the main window is not accessible (no possible interaction while the modal is open). Technical infos out of my kwin debug console, just listing what I think could be important: The main window: Is no modal, is normalWindow, is no popup, has resourceClass libreoffice-calc, is not transient, has windowType NET::Normal The validation popup: Is modal, is normalWindow, is no popup, has resourceClass libreoffice-startcenter (unsure about this one), is transient for the main window, has windowType NET::Normal. While activating that source input field no longer locks up the UI, it still causes the modal to become a real window (with a quick flash of the modal). The dimming in the parent window disappears, alt+tab enables me to switch between the main window and the validation popup. Tech infos, after breaking: The main window: Unchanged The validation popup (new entry, replaced previous): Is no modal, is normalWindow, is no popup, has resourceClass libreoffice-startcenter, is transient for the main window, has WindowType Net::Normal I'd conclude: The switch from modal to no-modal is either undesired (for activating the input field, not the shrink-button) or it should have never been a modal in the first place (to avoid the locking of the parent window). As said, it's nitpicking from my side. Inconsistent behaviour, being able to interact with the main window or not, depending if I clicked a specific input field in a modal. Logically speaking (I have no idea about the source) possible the reason for the first, already fixed, issue. Anyways, thanks for your time and effort, it's really appreciated! -- You are receiving this mail because: You are the assignee for the bug.
