-
Notifications
You must be signed in to change notification settings - Fork 51
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
Dashboard notification dismissed early #949
Comments
I can confirm the issue.
I am not certain what the ideal result should be when the the node is sent a new notification before the first has expired. |
The Vuetify snackbar component used for notifications does not have a queuing feature as it goes against the Material Design guidelines. As it seems, successive notifications replace the previous one which is not ideal when receiving multiple notifications. There is a Vuetify lab component to allow queuing in progress but seems to be still some way off from being usable. Here is an alternative third-party snackbar component that offers a rich set of features, including the ability to display multiple notifications at once. https://vuetify-sonner.vercel.app/ I believe this listed feature would help resolve #733 as well. Curious to know what your opinions are on using it in D2. |
As a workaround, once the enhancements described in pull request #932 have been released then one will be able to easily implement a queuing strategy around the node in node red so that they appear sequentially. |
This should be possible to build a workaround into the Dashboard-level logic, rather than relying on Vuetify to implement features for us. |
Current Behavior
Notification is triggered with 5 second timeout
Countdown bar starts to show progress
After 3 seconds another notification is triggered
The second notification replaces the first notification
Countdown bar starts to show progress again
After 2 seconds the notification disappears
Expected Behavior
The first notification should remain on screen for 3 seconds and then get replaced by the second triggered button click
The second notification should remain on screen for the full 5 seconds until the timeout countdown bar has completed
Steps To Reproduce
Add a button node and a trigger node and a notification node to the flow
Wire up to link the button node to the trigger node to the notification node
Set the repeat node to send a trigger then again after 3 seconds
Edit notification node to display top right for 5 seconds with a countdown bar
Click the button and observe the notification(s) for 5 seconds rather than 8 (3+5)
Environment
Have you provided an initial effort estimate for this issue?
I am not a FlowFuse team member
The text was updated successfully, but these errors were encountered: