Notification fade out without user input

[vaadin-bot]

Originally by alax

---

In some instances Notifications need to fade out without user input (keyboard stroke or mouse movement). Currently there is not way for fade out to occur without user input.
This enhancement has also been voiced by some of the members of the Vaadin community.

---

Imported from https://dev.vaadin.com/ issue #7344

[vaadin-bot]

Originally by @Artur-

---

Please describe the use case for this. Notifications do work this way on touch devices already so the only thing required would be an API to enable this behavior.

[vaadin-bot]

Originally by alax

---

I developed a site for crossfit gym. One of the functions is to keep track of attendance.
The attendance module has the following requirements:

1. User has access to keypad with numerics only (+ enter button)...no access to mouse or regular keyboard
2. User enters personal code to register attendance

3. On success:

   Notification displays the following message:

   "User" registered attendance successfully. This is your xx workout

   or

   "User" membership has expired....Plese contact sales rep.

   On failure:

   Failed to register "User" for attendance, please check input.

   In all instances the Notification should display for about 5 seconds and disappear without user interference so that the Notification will not interfere with next user about to log in.

[stale[bot]]

Hello there!

It looks like this issue hasn't progressed lately. There are so many issues that we just can't deal them all within a reasonable timeframe.

There are a couple of things you could help to get things rolling on this issue (this is an automated message, so expect that some of these are already in use):

• Check if the issue is still valid for the latest version. There are dozens of duplicates in our issue tracker, so it is possible that the issue is already tackled. If it appears to be fixed, close the issue, otherwise report to the issue that it is still valid.
• Provide more details how to reproduce the issue.
• Explain why it is important to get this issue fixed and politely draw others attention to it e.g. via the forum or social media.
• Add a reduced test case about the issue, so it is easier for somebody to start working on a solution.
• Try fixing the issue yourself and create a pull request that contains the test case and/or a fix for it. Handling the pull requests is the top priority for the core team.
• If the issue is clearly a bug, use the Warranty in your Vaadin subscription to raise its priority.

Thanks again for your contributions! Even though we haven't been able to get this issue fixed, we hope you to report your findings and enhancement ideas in the future too!

[stale[bot]]

The issue was automatically closed due to inactivity. If you found some new details to it or started working on it, comment on the issue so that maintainers can re-open it.