Graylog2 / Graylog2/graylog2-server
Toast messages should not autodismiss if I'm trying to interact with them
- Dominant language
- Java
- Stars
- 8.1k
- Forks
- 1.1k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 217
Description
When the user does something wrong, like [trying to edit stream rules when he's not supposed to](https://github.com/Graylog2/graylog2-server/issues/11007#issuecomment-1531309094) there's a toast message that auto dismisses. This makes interacting with them for copying, screen-shooting, etc. very tricky. The toast message should not auto-dismiss itself if I'm trying to interact with it.
## Expected Behavior
- User does something that triggers a toast message
- Toast message appear
- User hovers, clicks or otherwise starts interacting with the message
- The timer should restart from the start and stop while the user is interacting with it
## Current Behavior
- User does something that triggers a toast message
- Toast message appear
- User hovers, clicks or otherwise starts interacting with the message
- The toast disappear while the user is hovering, clicking or otherwise interested in the message content
## Possible Solution
- Make the toast self dismissing timer wait until the user stop interacting with it or loses focus, or
- If the user interacts with the toast message, just change the toast to be manually dismisseable only
- Make the timer longer or configurable (this is for those clients that may not interact with the message directly, since 3 seconds seems awfully short)
## Context
- When users are debugging issues with graylog, is useful to provide accurate information about the things that are happening. Making difficult for the user to provide the exact toast message, would lower the opportunity for the users to provide these kinds of information.
Contributor guide
Assessment
This issue has not been assessed yet.