-
Notifications
You must be signed in to change notification settings - Fork 397
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
CB-3015: adds an fadeout animation & min close delay time to all noti… #2306
CB-3015: adds an fadeout animation & min close delay time to all noti… #2306
Conversation
i also can suggest to not to show notification right when some process started |
let closeDelay = 0; | ||
let closeDelay = MIN_CLOSE_DELAY; | ||
|
||
if (notification.type !== ENotificationType.Error && !notification.persistent && notification.autoClose !== false) { | ||
closeDelay = FADE_TIMEOUT; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's possible that we now broke this behavior (that some notifications must be closed instantly and some not)
and we have two different delays
now, all notifications will be closed after MIN_CLOSE_DELAY
even when we want them to be open
check useActivationDelay
in Snackbar
…ng-from-a-database-for-more-time
…ng-from-a-database-for-more-time
…00ms" This reverts commit 184aae7.
…ng-from-a-database-for-more-time
No description provided.