-
Notifications
You must be signed in to change notification settings - Fork 8
Date and Delete button cut off or sometimes not even there #35
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
Comments
Does this happen when the text doesn't contain any spaces? |
Thanks for getting back to me. Yes, the first issue (image above) happens when the text (in a line) doesn't contain any spaces at all or there aren't any spaces in the first 80 characters. The issue with no delete button at all, there are definitely spaces. The next time I come across such a message (usually sent by Proxmox when apticron has new packages available), I'll keep that message around and add more info here. P.S.: More info to maybe narrow down the issue: The gotify UI shows all messages correctly (with date and delete button). |
So, it seems that I currently can't reproduce the 2nd issue where there is no delete button at all. |
Thanks for letting me know. I'm trying handle cut off in #36 by displaying wide messages in a different widget that does better word wrapping, so at least it doesn't break the UI. The downside is that I can't get that widget to fit the height of the message. |
Depending on the message the date and/or the delete button are either cut off but still there, if you make the gotify-tray window wider, or they are not there no matter what (even if you scroll the message to the right or make the window bigger).
In the example above the date and the delete button will show, when I make the window wider.
I currently don't have a message where there is no delete button at all, but I will update this issue as soon as I do.
I am not sure whether this has something to do with the new gotify server release 2.6.1 or whether I just never encountered this before.
The text was updated successfully, but these errors were encountered: