I have a problem with notifications. I need them to disappear without user interference i.e. the user keys in his key code (numerics only)
and presses enter. On success the Notification displays (“success mr. user”) or (“error on input”). I tried using Refresher addon but
Tomcat seems to need frequent restarts now. Is there some simple way to fake user input so the Notification will fade on delay without user
input ? Any feedback is greatly appreciated.
The humanized notification does not fade away
without user input . You must move the mouse or hit a key for the fade-out timer to start. As far as I know, there is no way to do this with Vaadin notifications.
Implementing
#7020 would make it possible to customize this yourself with minimal client side coding, but you could in any case
create an enhancement request for this specific case - I have heard this request from someone else as well, but “as long as there is no ticket, there is no problem” applies as always.
Thanks all for your quick reply. I created an enhancement request as suggested. Hopefully it was done correctly as this was my first ticket -_-
Ticket #7344
Is there any solution to this problem? Ticket was created almost 1 year ago and still all notifications in sampler won’t disappear unless one moves his mouse.
I also need the future (notification that will disappear on its own after the specified delay) of showing notification in no-user-input/limited-user-input application
Nothing done for
#7344 . The default behavior should not be changed in any case, but there could be an option for this.
On the other hand,
#7020 has been implemented so it should be possible to do this with some custom client side coding in your application by replacing VNotification using GWT deferred bindings.
Thank you for quick answer! I will try to use your suggestion, but it’s gonna be hard i feel
I understand the default behavior is such so the user don’t miss any notification (if he is away for example), but there are
a lot of possible applications, where there won’t be any user interaction at all, so IMHO such option (to activate delay after creation not after first user action from creation) is a must have.