[Alert] Multiple open
Alerts present in DOM at initialization should form a queue
#9340
Open
2 of 6 tasks
Labels
0 - new
New issues that need assignment.
c-alert
Issues that pertain to the calcite-alert component
Calcite (design)
Issues logged by Calcite designers.
calcite-components
Issues specific to the @esri/calcite-components package.
enhancement
Issues tied to a new feature or request.
impact - p2 - want for an upcoming milestone
User set priority impact status of p2 - want for an upcoming milestone
needs triage
Planning workflow - pending design/dev review.
Check existing issues
Description
If multiple Alert with the
open
property are present in the DOM as the components initialize, they will not form a queue, and appear stacked on top of one another.Subsequently added Alert will "fix the queue" and properly stack Alert, but this doesn't happen at load.
Acceptance Criteria
If there are multiple Alert with the
open
property present in the DOM as the components initialize, they should form a queue. As there currently isn't a way to manage order, we might just use "last one wins" like we do in other components that have multiple sibling components that can load simultaneously.Relevant Info
Further improvements may occur in #8705, but it would be nice to solve this with our current set up... might require the addition of an Alert Group to manage?
Which Component
Alert
Example Use Case
Codepen:
https://codepen.io/mac_and_cheese/pen/xxNGjVe?editors=1000
Note that on load the two Alert are stacked on top of one another, each unaware of the other's existence. If you "Add an Alert" - it will correctly create a queue with 3 Alerts.
Priority impact
p3 - want for upcoming milestone
Calcite package
Esri team
Calcite (design)
The text was updated successfully, but these errors were encountered: