-
-
Notifications
You must be signed in to change notification settings - Fork 962
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
Allow hiding "You are disconnected from the internet" message in the settings. #3768
Comments
Thank you very much for opening up this issue! I am currently a bit overwhelmed by the many requests that arrive each week, so please forgive me, if I fail to respond personally. I am still very likely to at least skim read your request and I'll probably try to fix all (real) bugs if possible and I will likely review every single PR being made (please, give me a heads up if you intent to do so) and I will try to work on popular requests (please upvote via thumbs up on the original issue) whenever possible, but trying to respond to every single issue over the last years has been kind of draining and I need to adjust my approach for this project to remain fun for me and to make any progress with actually coding new stuff. Thanks for your understanding! |
Before adding this, we need to evaluate, what might be affected by this (issue integrations and sync). We generally should aim to handle this more gracefully (maybe ditching the banner completely and only providing the info when a request is attempted). |
Maybe something like a network icon that indicates a network connection would be good? |
That is a good idea! Maybe it could replace the sync icon when shown. |
Problem Statement
When I am not connected to the internet everytime I open a new superProductivity instance it shows me a message.
❔ Possible Solution
Make a toggle that allows hiding this banner.
Make it auto-dismiss after a few seconds.
Add a option for "Dont show again" besides the current "Dismiss".
➕ Additional context
I am using the Flatpak version.
The text was updated successfully, but these errors were encountered: