-
Notifications
You must be signed in to change notification settings - Fork 406
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Window always on top on disconnect #614
Comments
Which popup window is this? Could you post an image showing the offending Window? |
Here's a short video: |
To be fair my workaround now is to just ESCape once it pops up and then reconnect later, but still I would prefer to leave it open in the background, esp. since it was possible in the past. |
Cancel and try again takes the almost the same effort as manually sending it to the background. We work under the assumption that VPN connection is a critical piece and most users would want to attend to it promptly to avoid a disconnection. So, I'm not convinced that removing "TOPMOST" property from the password popup window would be a good idea. By the way that auth popup is likely after auth-token expiry which triggers a new of 2FA prompt. Your server admin could use a longer token expiry and require 2FA only once in 24 hours or so if that is acceptable. |
Since one of the recent updates (approx. in the last half to 3/4 year) the window that pops up on disconnect to reconnect is always on top and can't be in the background (of the stack of windows).
This is quite annoying to me, as I'm sometimes busy with whatever was in the foreground at that moment and don't want and need to immediately deal with the disconnected VPN.
If this is intended: Is there an option to restore the previous behavior of being able to put in the background, e.g. by focusing another window?
(Had a look through the settings, didn't find it.)
If not: Please fix 0:-)
I'm on Windows 10 22H2 and have recently updated OpenVPN from a version from approx. last summer where this was possible to 2.6.1.
Current versions:
The text was updated successfully, but these errors were encountered: