Latest solutions
Product feedback app (Next.js App Router, RSC, Tailwind, Supabase)
#next#react#tailwind-cssSubmitted over 1 year agoI've added loading states to buttons that trigger server actions and they work well. But I couldn't figure out how to add the loading states for page navigations and page revalidations. Optimistic updates seem to be one choice, but I prefer loading states. Any help or feedback regarding the loading states and the entire app in general are much appreciated, thanks!
Todos App (Next.js, react-beautiful-dnd, Tailwind, Local storage)
#next#react#tailwind-css#accessibilitySubmitted over 1 year agoEntertainment web app (React, Next.js, Tailwind, TMDB API)
#next#react#tailwind-cssSubmitted over 1 year agoRest Countries API (Next.js, Tailwind)
#next#react#tailwind-css#accessibilitySubmitted almost 2 years agoEcommerce product page (React and Tailwind)
#react#tailwind-css#accessibilitySubmitted almost 2 years ago
Latest comments
- @abhijithmuthyala@abhijithmuthyala
Update: Added the experimental
view transitions
and just like that, the links menu, cart and lightbox all animate with a nice default fade animation! Works in chrome 111+. - @abhijithmuthyala@abhijithmuthyala
I'm not sure why the design comparision doesn't match here. I'm using Polypane browser which has the design image overlay feature, and my solution matches perfectly (almost) in it.
- @atmahana@abhijithmuthyala
I can reproduce the issue, but if you keep the dev tools opened, the app somehow works as intended. Infact, when the dev tools is kept open, I got different responses even though I was clicking very fast. This is super weird indeed.
- @MelvinAguilar@abhijithmuthyala
Hi, the loading spinner looks great! Few things I noticed:
-
The loading spinner keeps animating even when it is not visible, which might be unnecessary. Changing the animation declaration on
.loader::before
to.loader.visible::before
would only animate it when it is visible. -
While operating through keyboard (Enter / Spacebar), the focus state on the button is lost. I think it would be better to reset the focus back onto the button for better accessibility.
-
I've also been learning about accessibility, and from what I understand, setting
aria-live
topolite
instead ofassertive
would be better since it doesn't interrupt what the screen reader is currently reading - More info on MDN. I usedaria-live='polite'
on the new advice text in my solution and the screen reader(NVDA) reads out the new advice.
Marked as helpful -