coracle/flotilla
1
6
Fork 23
Code Issues 40 Pull Requests 2 Actions Packages Projects 5 Releases Wiki Activity

Refine toast #137

New Issue
Closed
opened 2026-04-03 16:44:22 +00:00 by hodlbod · 3 comments
hodlbod commented 2026-04-03 16:44:22 +00:00
Owner
Copy Link
Copy Source

From #133

  • Remove the x button (actually, see if we can move it to the top right of the toast)
  • Swipe to dismiss
  • On mobile, move it to the top of the page so it doesn't cover navigation elements

@0xNaman, do you have any opinions about this approach?

From https://gitea.coracle.social/coracle/flotilla/issues/133 - [ ] Remove the x button (actually, see if we can move it to the top right of the toast) - [ ] Swipe to dismiss - [ ] On mobile, move it to the top of the page so it doesn't cover navigation elements @0xNaman, do you have any opinions about this approach?
hodlbod added this to the Current milestone 2026-04-03 16:44:22 +00:00
hodlbod added the design label 2026-04-03 16:44:22 +00:00
0xNaman commented 2026-04-03 17:40:02 +00:00
Copy Link
Copy Source

  1. That approach makes sense to me. Removing the x button solves the ambiguity I ran into, and auto-dismiss with swipe-to-dismiss feels like the right default. It also matches how most mobile users expect toasts to work.

  2. Moving it to the top on mobile is a good call, right now it competes with the bottom nav. On desktop, I think top right would probably work since that is where most web apps like Slack, Discord put their notifications.

  3. One other thing to consider "Sending..Cancel" toast specifically, If x, cancel button is removed on that one, the user loses the ability to cancel mid-send. Maybe confirmations auto-fade after a couple seconds, but action toasts like sending stay visible until the action completes?

1. That approach makes sense to me. Removing the x button solves the ambiguity I ran into, and auto-dismiss with swipe-to-dismiss feels like the right default. It also matches how most mobile users expect toasts to work. 2. Moving it to the top on mobile is a good call, right now it competes with the bottom nav. On desktop, I think top right would probably work since that is where most web apps like Slack, Discord put their notifications. 3. One other thing to consider "Sending..Cancel" toast specifically, If x, cancel button is removed on that one, the user loses the ability to cancel mid-send. Maybe confirmations auto-fade after a couple seconds, but action toasts like sending stay visible until the action completes?
hodlbod commented 2026-04-03 17:44:24 +00:00
Author
Owner
Copy Link
Copy Source

We'll keep the cancel button, but not the x. Or maybe we could reposition it to the top-right of the toast so it's clear what it is. Toast generally does auto-dismiss, but certain ones (like the cancel one) persist until complete.

We'll keep the cancel button, but not the x. Or maybe we could reposition it to the top-right of the toast so it's clear what it is. Toast generally does auto-dismiss, but certain ones (like the cancel one) persist until complete.
👍 1
hodlbod added dev and removed design labels 2026-04-03 17:45:05 +00:00
userAdityaa self-assigned this 2026-04-03 20:57:14 +00:00
userAdityaa commented 2026-04-03 21:19:48 +00:00
Collaborator
Copy Link
Copy Source

Hey, since this was initially marked as design-first to confirm the approach and is now moved to dev, I’ve self-assigned it and opened PR #148. If there’s any feedback regarding the design or adjustments needed, please let me know.

Hey, since this was initially marked as design-first to confirm the approach and is now moved to dev, I’ve self-assigned it and opened PR #148. If there’s any feedback regarding the design or adjustments needed, please let me know.
👍 1
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
design
For issues related to design work. Development should be done in another issue and refer back to this one.
 dev
Issues related to development work
 easy
Issues that can be executed on by new contributors
 idea
For issues that aren't yet actionable
 priority
For issues related to high priority features and bugs
 usability
Issues that have to be validated with real live human beings.
No Label dev
Milestone
No items
No Milestone Current
Projects
Clear projects
No project
Assignees
Clear assignees
hodlbod (hodlbod) mplorentz (Matt Lorentz) sakshamjain (Saksham Jain) sondreb triesap userAdityaa (Aditya Chaudhary)
No Assignees userAdityaa
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coracle/flotilla#137
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?