Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Enhancement: calcite-alert - options for seeing queued messages without dismissing them #2835

Open
hccampos opened this issue Aug 17, 2021 · 18 comments
Open

Enhancement: calcite-alert - options for seeing queued messages without dismissing them #2835

hccampos opened this issue Aug 17, 2021 · 18 comments
Assignees
@jcfranco
Labels
1 - assigned Issues that are assigned to a sprint and a team member. ArcGIS Maps SDK for JavaScript Issues logged by ArcGIS SDK for JavaScript team members. ArcGIS Online Issues logged by ArcGIS Online team members. c-alert Issues that pertain to the calcite-alert component design Issues that need design consultation prior to development. enhancement Issues tied to a new feature or request. p - medium Issue is non core or affecting less that 60% of people using the library ready for dev Issues ready for development implementation. spike Issues that cannot be estimated well enough until the team has done further research
Milestone
2024-07-30 - Jul ...

Comments

@hccampos
Copy link

hccampos commented Aug 17, 2021 •
edited by eriklharper

Description

We are using the <calcite-alert> in order to display errors, warnings or success messages. However, it has been reported that collapsing all the messages into a single one (with the indicator showing how many messages are present) is not ideal since it forces users to close messages in order to see what other messages may be available.

It would be interesting to have a way of looking at other messages without dismissing them. Two main possibilities to explore:

  • Allow expand a queue to view all currently queued alerts.
  • Prop to decide on whether to stack or queue alerts, style guardrails to prevent 20 alerts from taking over an entire page.

CC @yannikmesserli

SVCH
@hccampos hccampos added 0 - new New issues that need assignment. enhancement Issues tied to a new feature or request. needs triage Planning workflow - pending design/dev review. labels Aug 17, 2021
@hccampos hccampos changed the title Enhancement: calcite-alert - show Enhancement: calcite-alert - options for seeing queued messages without dismissing them Aug 17, 2021
@julio8a julio8a added design Issues that need design consultation prior to development. and removed needs triage Planning workflow - pending design/dev review. labels Sep 24, 2021
@julio8a julio8a added this to the Sprint 9/27 – 10/8 milestone Sep 24, 2021
@jcfranco
Copy link
Member

Please add your planning poker estimate with ZenHub @macandcheese

@macandcheese
Copy link
Contributor

Needs design - in progress.

@macandcheese
Copy link
Contributor

macandcheese commented Oct 25, 2021 •
edited

@hccampos here is an initial comp - spacing, interaction, display not finalized - would this more or less solve (obviously lots to question around .. max number displayed, scrolling when "too many alerts", do you display the chip count while expanded, etc.):

Screen Shot 2021-10-25 at 10 17 43 AM

@jcfranco would this necessitate the creation of an "alert-wrapper" component to handle positioning and "added UI" to handle multiple (related - #3033)?

@macandcheese macandcheese mentioned this issue Oct 25, 2021
Closed
@hccampos
Copy link
Author

IMHO, that looks nice @macandcheese, but I'll defer to @janett-baresel and @yannikmesserli on this one.

@janett-baresel
Copy link

Looks very good to me. Thanks!

@macandcheese
Copy link
Contributor

Thanks all. Will continue to work and iterate on this and ping this thread when more final designs are ready for testing / feedback.

@macandcheese macandcheese mentioned this issue Dec 2, 2021
Closed
2 tasks
@macandcheese macandcheese self-assigned this Jan 5, 2022
@macandcheese macandcheese mentioned this issue Jan 26, 2022
Closed
@macandcheese
Copy link
Contributor

@jcfranco - I think you mentioned you had an idea for this that wouldn't require a wrapping calcite-alerts / calcite-alert-group.

Could you expand on that (alert queue pun alert 🚨 )? Multiple items may need to be positioned in a single fixed container along with "extra UI elements", I am not sure the best way to achieve that without some kind of wrapping parent to control placement and manage expand / close and associated animations.

jcfranco added a commit that referenced this issue Nov 17, 2023
@jcfranco
revert: feat(alert): make component responsive
c3c72df 
Roll back alert responsiveness (#7755) in favor of upcoming alert queue UX (#2835)
jcfranco added a commit that referenced this issue Nov 17, 2023
@jcfranco
revert: feat(alert): make component responsive
52bb096 
Roll back alert responsiveness (#7755) in favor of upcoming alert queue UX (#2835)
@jcfranco jcfranco mentioned this issue Nov 17, 2023
Merged
@SkyeSeitz SkyeSeitz mentioned this issue Nov 17, 2023
Closed
4 tasks
jcfranco added a commit that referenced this issue Nov 21, 2023
@jcfranco
revert: feat(alert): make component responsive (#8195)
2f4ff6c 
**Related Issue:** N/A

## Summary

Rolls back responsiveness (#7755) in favor of upcoming alert stack UX
(#2835).

See
#7921 (comment)
for more info.
benelan pushed a commit that referenced this issue Nov 24, 2023
@jcfranco @benelan
revert: feat(alert): make component responsive (#8195)
19cf05f 
**Related Issue:** N/A

Rolls back responsiveness (#7755) in favor of upcoming alert stack UX
(#2835).

See
#7921 (comment)
for more info.
benelan pushed a commit that referenced this issue Nov 24, 2023
@jcfranco @benelan
revert: feat(alert): make component responsive (#8195)
330eb44 
**Related Issue:** N/A

Rolls back responsiveness (#7755) in favor of upcoming alert stack UX
(#2835).

See
#7921 (comment)
for more info.
benelan pushed a commit that referenced this issue Nov 26, 2023
@jcfranco @benelan
revert: feat(alert): make component responsive (#8195)
bb017ed 
**Related Issue:** N/A

Rolls back responsiveness (#7755) in favor of upcoming alert stack UX
(#2835).

See
#7921 (comment)
for more info.
@paulcpederson paulcpederson mentioned this issue Dec 1, 2023
Open
6 tasks
@ashetland
Copy link

ashetland commented Dec 5, 2023 •
edited

Surfacing designs for this since GitHub was hiding them in the thread. Could be coupled with #8316.

@brittneytewks brittneytewks added the design Issues that need design consultation prior to development. label Dec 11, 2023
@geospatialem geospatialem added the spike Issues that cannot be estimated well enough until the team has done further research label Jan 8, 2024
@geospatialem geospatialem added 1 - assigned Issues that are assigned to a sprint and a team member. and removed 0 - new New issues that need assignment. labels Jan 8, 2024
@geospatialem geospatialem mentioned this issue Feb 7, 2024
Open
8 tasks
@macandcheese macandcheese added the c-alert Issues that pertain to the calcite-alert component label May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jcfranco jcfranco

Labels
1 - assigned Issues that are assigned to a sprint and a team member. ArcGIS Maps SDK for JavaScript Issues logged by ArcGIS SDK for JavaScript team members. ArcGIS Online Issues logged by ArcGIS Online team members. c-alert Issues that pertain to the calcite-alert component design Issues that need design consultation prior to development. enhancement Issues tied to a new feature or request. p - medium Issue is non core or affecting less that 60% of people using the library ready for dev Issues ready for development implementation. spike Issues that cannot be estimated well enough until the team has done further research
Projects
None yet
Milestone
2024-07-30 - Jul Release
Development

No branches or pull requests