Async notification never dissapears about vue-snotify HOT 9 CLOSED

I am having the same issue. Is this normal behaviour?
This first time it disapears, but the second time it's not.

from vue-snotify.

anything new on this topic? I also have the same issue

from vue-snotify.

@artemsky
Can you provide an update on the status of the current issue?

from vue-snotify.

I'm also seeing this issue quite frequently. I've resorted to calling clear in some places to get around it but it certainly isn't ideal in the slightest.

On a side note, I still think this project r0x! :D

from vue-snotify.

I am also having this issue with Vue-Snotify v3.0.4 and Vue v2.5.16. However, looking at the documentation I found that if you add a config after your promise function, the timeout starts working. { title:'', body:'', () => new Promise(), { timeout: 3000 } }. While it would be nice if it functioned on the timeouts provided in the resolve/reject of the Promise, this is at least a way to get it working again.

from vue-snotify.

Sorry guys. I have not been with you for a long time.
But now I'm back.
Soon I will update the library in accordance with all the comments.

from vue-snotify.

Dealing with this more the async toast appears to only respond to the timeout of the initial config and not the resolve/reject configs

from vue-snotify.

Look through the code and watching in debug, all the config settings are properly copied over from the resolve/reject of the passed in Promise. However, I am having trouble identifying where the controls associated with the timeout are supposed to be set. Forgive me, first time actually using typescript so it took me a bit to walk through the code. @artemsky

from vue-snotify.

Is there any workaround available?

from vue-snotify.