- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 246
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
[Feature Request] Add Window Controls to new Discord Title Bar #1077
Comments
for now you can unenroll yourself from the visual refresh experiment by enabling the experiments plugin & setting yourself to 'Not Eligible' for the "Desktop Visual Refresh" experiment. Use the support channel if you need more help in doing so. |
wow, thanks! |
This will likely not be fixed until this redesign gets fully rolled out and becomes stable. right now it's only an in development experiment Discord is doing, so it is still subject to frequent change |
Would it be a good idea to migrate to patching the module containing the wrappers for the buttons? I'm willing to do this, in addition to adding support for the windowKey argument that these methods consume (so window buttons in popouts work properly) |
Seems like it's rolling out widely starting today |
Title bar def needs being fixed since it broke after the update |
Just got the update myself and I have the same issue. It's too big... Let us (the users) customize more in the client, if you're going to TOS-force us to one client. |
redesign is rolling and and broke the title bar |
yes we know. this will be fixed soon, just have patience |
It's really annoying |
Discord Account
keqwerty
Motivation
So Discord just released a new UI without any choice. There are no window control buttons on Linux when I use Discord's title bar (I can't disable it because the default frame window system on Wayland works weird)
https://i.imgur.com/q7A4EJn.png
Solution
Just add new window control buttons to Discord Title Bar
Alternatives
N/A
Additional context
No response
Request Agreement
The text was updated successfully, but these errors were encountered: