You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Task Description
Currently, we do not have a comprehensive, usabel notification ssystem that allows developers to create light weight, short-lived/transient messaging and confirmation to end users about results of their actions.
We have created a Toast component that represents an actual notification, but we have no integrated nor comprehensive context that would manage, place, or position these in the context of an application in place.
In order to remedy that situation and make notifications usable for developers in a comprehensive and consistent manner, we should:
Sub-tasks
Rename Toast component to Notification
Create a NotificationManager component, that creates and removes notifications and places them in the DOM (some thoughts/directions below, exact specs TBD)
Research a11y needs and concerns, and implement with Notification accordingly
Create subtasks accordingly when working on this.
Some (preliminary, validate before actually implementing!) requirements/specs:
Notifications should always be in front (z-axis) any other UI elements, even those which are rendered into a portal using PortalProvider (use highest z-index, use dedicated container that is rendered after the parent of portal containers rendered by PortalProvider, ideally combine both approaches)
Multiple notifications can exist at any point in time. These should stack up vertically and not cover each other. (-> render all into the same portal-container or similar element)
Notification duration, placement, and other parameters should be props of the NotificationManager, however some individual notifications should be able to accept their own props and override the global settings.
Notifications should be positioned relative to the viewport, so they stay at the same position relative to the browser window when scrolling or resizing
Related Issues #691 could easily be satisfied with this component once completed.
The text was updated successfully, but these errors were encountered:
Task Description
Currently, we do not have a comprehensive, usabel notification ssystem that allows developers to create light weight, short-lived/transient messaging and confirmation to end users about results of their actions.
We have created a
Toast
component that represents an actual notification, but we have no integrated nor comprehensive context that would manage, place, or position these in the context of an application in place.In order to remedy that situation and make notifications usable for developers in a comprehensive and consistent manner, we should:
Sub-tasks
Toast
component toNotification
NotificationManager
component, that creates and removes notifications and places them in the DOM (some thoughts/directions below, exact specs TBD)Notification
accordinglyCreate subtasks accordingly when working on this.
Some (preliminary, validate before actually implementing!) requirements/specs:
PortalProvider
(use highest z-index, use dedicated container that is rendered after the parent of portal containers rendered byPortalProvider
, ideally combine both approaches)Related Issues
#691 could easily be satisfied with this component once completed.
The text was updated successfully, but these errors were encountered: