-
Notifications
You must be signed in to change notification settings - Fork 77
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
Enhancement: Alert - provide various placement options #3033
Comments
I think this is reasonable. I wonder if a slot within the shell makes sense for this, so the positioning could be controlled absolutely. Currently, it's a fixed position item which prevents the alert from staying affixed to a shell that is not full-screen (which, may be good in some cases, and not in others, so some affordance to choose this?) I feel like we'd probably want to limit the options to top center/start/end, bottom center/start/end. Another thing to consider would be what happens on mobile - currently we constrain max width and start / end positioned alerts at small scale may just need to become full-width. |
Here's an initial comp with the proposed locations - would this be acceptable @hccampos? Some thoughts while working on these: I wonder if alerts placed "top" would benefit from having their accent border flipped (as well as animations flipping). This likely has implications with #2835 - to visually change the direction of the stack, and ui around multiple). |
I mentioned #2835 above - while this issue may inform that one, this one can proceed - that's not a blocker and this is a reasonably simple add. |
Installed and assigned for verification. |
verified on beta.74 in the doc sample https://developers.arcgis.com/calcite-design-system/components/alert/#sample |
Description
We would like to be able to place alerts in different locations.
Acceptance Criteria
<calcite-alert>
should have a property/attribute to specify its placement.Relevant Info
Which Component
<calcite-alert>
Example Use Case
SVCH
The text was updated successfully, but these errors were encountered: