Use case: my node.js server hangs from time to time (runs in the Windows Subsystem for Linux). When the server hangs, the front-end web page notifies me that the changes can’t be saved (and there is even a counter showing how many times it tried). However, for the few minutes while I restart the node.js server (it does take a while), I can still use the front-end, search and even make changes; the changes will be saved when the service is back up.
The challenge is the notification bubble hides the tiddler titles and a good portion of the start of the tiddler. It would be helpful if I could move the notification around or close it (even though in this case, it would likely re-appear with the counter increment).
@Maurycy already, my bad. Thanks…
Interestingly, the demo here has a dismiss button… I will investigate and try a few things about alerts when I have chance.
Should I remove my post from here? done by @pmario
Some useful information here in this screen capture… investigating why the close button isn’t shown, whereas it is on the TiddlyWiki.com demo. It may be related to plugin conflict, my own notebook seems to consistently not show the close button…
most likely as defined in: $:/.giffmex/.Stylesheet4Stroll
html body.tc-body .tc-image-cancel-button {stroke: white;fill:#ffdd55;}
easy fix…
I will still investigate ways to move the notification around or a smarter “dismiss” that prevents repeated errors from re-appearing after being dismissed (perhaps)…
Hi all. I, too, have found the alert banner too intrusive. I created an alert-suppression plugin that suppresses the alert banner if it repeats, as it does when the server connection is broken. It shows the banner initially to alert the user, and the sync icon continues to show red, but the banner then gets out of the way so you can edit without the banner interfering. There is a checkbox in the plugin settings to enable or disable suppression.