-
Notifications
You must be signed in to change notification settings - Fork 669
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
[Linux] "Cancel account setup" dialog not modal #11032
Comments
fmoc
added
type:bug
p2-high
Escalation, on top of current planning, release blocker
labels
Jul 12, 2023
Can't reproduce on Windows, or mac. |
Smells like a Qt bug. |
TheOneRing
added
p3-medium
Normal priority
and removed
p2-high
Escalation, on top of current planning, release blocker
labels
Aug 2, 2023
Needs to be tested on Wayland. |
michaelstingl
changed the title
"Cancel account setup" dialog not modal
[Linux] "Cancel account setup" dialog not modal
Dec 19, 2023
2 tasks
Merged
Tested with Confirmation dialog is always on top of new account setup window |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Pre-submission Checks
Describe the bug
When canceling the account setup, a dialog is shown asking for confirmation. It's possible to click on the setup wizard again, which thereafter effectively hides the confirmation dialog. To be able to access it again, one has to move it out of the way. Clicking on the item in the taskbar or using the systray to show the UI do not yield a different result.
Expected behavior
The cancel dialog must be a mandatory modal dialog that is always shown above all other windows.
Steps to reproduce the issue
No response
Screenshots
Logs
No response
Client version number
Build made from latest
master
. Should affect the current dailies, too.Desktop environment (Linux only)
No response
Client package version and origin (Linux only)
No response
Installation path (Windows only)
No response
Server information
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: