Building a Toast Component
emilkowal.ski
Building a Toast Component
1–10 of 45 posts
Re: Building a Toast Component
#2Scrolling that web site on mobile is really choppy.
Re: Building a Toast Component
#3Scrolling that web site on mobile is really choppy.
Perfectly smooth on iOS for me.
Re: Building a Toast Component
#4Scrolling that web site on mobile is really choppy.
VERY laggy on Android FF.
Re: Building a Toast Component
#5Scrolling that web site on mobile is really choppy.
Perfectly smooth on Android FF.
Re: Building a Toast Component
#6Scrolling that web site on mobile is really choppy.
Exploded my mobile browser on Android.
Re: Building a Toast Component
#7Meanwhile, GitHub is removing Toasts from Primer, their design system.[1] They’re next to impossible to implement in a way that retains accessibility across all needs, and if you try to restrict their usage to places where accessibility doesn’t matter so much (simple ephemeral confirmations) people misuse them anyway.
It’s notable that accessibility isn’t mentioned once in this post, or, in fact, in the component’s documentation.
Re: Building a Toast Component
#8Toasts are a great way to lose information. They are a terrible design and should not be used. They distract the user, are not dense with information, and provide no value. If a message is important enough for the user to read, it should be a dialog box.
Re: Building a Toast Component
#9Scrolling that web site on mobile is really choppy.
Looking at the replies to your comment makes me think that maybe the browser software isn't the only factor that impacts website perf.
Re: Building a Toast Component
#10[deleted]