-
Notifications
You must be signed in to change notification settings - Fork 13
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
Allow Toast notifications to stack #428
Labels
4 - Done
Code has been added to the repository, and has been reviewed by a team member
Accessibility
Represents issues that are related to accessibility in UI such as WCAG, etc.
Bug
Issues where something has happened which was not expected or intended
ChocolateyCentralManagement
Comments
st3phhays
added a commit
to st3phhays/choco-theme
that referenced
this issue
Nov 15, 2024
st3phhays
added a commit
to st3phhays/choco-theme
that referenced
this issue
Nov 20, 2024
st3phhays
added a commit
to st3phhays/choco-theme
that referenced
this issue
Nov 21, 2024
st3phhays
added a commit
to st3phhays/choco-theme
that referenced
this issue
Nov 21, 2024
This allows multiple Toast notifications to stack on top of each other. They are only removed from the dom after the `hide` callback is triggered. This gives the user the ability to see all of the notifications that have been triggered.
st3phhays
added a commit
to st3phhays/choco-theme
that referenced
this issue
Nov 21, 2024
This allows multiple Toast notifications to stack on top of each other. They are only removed from the dom after the `hide` callback is triggered. This gives the user the ability to see all of the notifications that have been triggered.
st3phhays
added a commit
to st3phhays/choco-theme
that referenced
this issue
Dec 3, 2024
This allows multiple Toast notifications to stack on top of each other. They are only removed from the dom after the `hide` callback is triggered. This gives the user the ability to see all of the notifications that have been triggered.
st3phhays
added a commit
to st3phhays/choco-theme
that referenced
this issue
Dec 6, 2024
This allows multiple Toast notifications to stack on top of each other. They are only removed from the dom after the `hide` callback is triggered. This gives the user the ability to see all of the notifications that have been triggered.
st3phhays
added a commit
to st3phhays/choco-theme
that referenced
this issue
Dec 10, 2024
This allows multiple Toast notifications to stack on top of each other. They are only removed from the dom after the `hide` callback is triggered. This gives the user the ability to see all of the notifications that have been triggered.
st3phhays
added a commit
to st3phhays/choco-theme
that referenced
this issue
Jan 14, 2025
This allows multiple Toast notifications to stack on top of each other. They are only removed from the dom after the `hide` callback is triggered. This gives the user the ability to see all of the notifications that have been triggered.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
4 - Done
Code has been added to the repository, and has been reviewed by a team member
Accessibility
Represents issues that are related to accessibility in UI such as WCAG, etc.
Bug
Issues where something has happened which was not expected or intended
ChocolateyCentralManagement
Checklist
What You Are Seeing?
Toast notifications use one element which the text is appended to every time a new notification needs shown. In most cases, this is fine, but it becomes a problem if more than one Toast notification needs to be shown at a time. For instance, maybe two operations were done back to back, and they both need either a success/fail notification.
What is Expected?
Toast notification should be added one by one when they are needed. After they have been dismissed (either manually, or after the time limit), then they should be removed from the dom. This will allow Toast notifications to stack, and more than one to be shown at a time.
How Did You Get This To Happen?
I ran into this issue when needing to save a Deployment Step and show a "Saved Success Message" and then immediately go to duplicate a Step and show an other "Successful Duplication" message. When doing this, the first notification was immediately replaced, and was unable to be seen or announced by screen readers.
System Details
choco-theme 0.13.1
Installed Packages
Output Log
Additional Context
No response
┆Issue is synchronized with this Gitlab issue by Unito
The text was updated successfully, but these errors were encountered: