https://bugs.kde.org/show_bug.cgi?id=509990
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #15 from [email protected] --- (In reply to Zamundaaa from comment #12) > (In reply to Shariar Rahman from comment #11) > > Issue 1: The "leave" menu brought about using ctrl+alt+del doesn't get > > focus. > > > > Steps to reproduce: > > - Set focus stealing prevention to medium > > - Open a window and keep it in focus (tried with Firefox and Dolphin). > > - ctrl+alt+del to bring up "leave" menu > > - menu is not navigable by keyboard. Typing something actually brings up > > krunner in the background behind the blurred "Leave" menu > The logout greeter is started as a new process, it should be able to get > activation through the shortcut... It currently doesn't show up at all in my > dev session, so someone else will need to take a closer look at it. > > > Issue 2: Password prompts for KDE Vault or new WiFi connection opened after > > clicking through buttons on the system tray don't steal focus. > > > > Steps to reproduce: > > - Set focus stealing prevention to medium > > - Try to unlock a previously created and locked vault on KDE Vault > > - The prompt to enter password appears but doesn't steal focus. Must > > manually click in password box before entering. > That one is known. The network manager ones are especially annoying, because > we don't open the window directly, rather it's NetworkManager just prodding > things from the background. > > > Issue 3: New windows for GTK apps don't open in front. Not observed in QT > > apps (Tested Dolphin and Konsole) > > > > Steps to reproduce: > > - Set focus stealing prevention to medium > > - Open any GTK app window (Tested Firefox, Libreoffice, Xournal and PDF > > Arranger) > > - Open new window of the same app (often ctrl+n shortcut) > > - New window opens behind first window > Firefox is already fixed upstream, but for normal GTK apps this needs to be > reported to GTK. > > > I understand Low is supposed to be default, but the focus prevention should > > not be so intense on Medium. > Unfortunately the status quo is that many apps don't activate windows at > all, or do it only in a broken way - and aside from some heuristics to work > around broken apps in some situations (which we do on medium), the only > thing that could be done is to unconditionally give new windows focus. How would an app activate itself when its tray icon (or tray icon context menu action) is clicked? It doesn't receive an activation token like it does when e.g. notification is clicked, and it can't request a token from compositor because it's not in focus at that moment. -- You are receiving this mail because: You are watching all bug changes.
