Latest solutions
Responsive landing page using astro, vue and tailwind
#astro#tailwind-css#vue#jestSubmitted about 2 years agolanding page with alternating feature blocks
#astro#tailwind-css#accessibilitySubmitted about 2 years agoAdvice genrator app using preact, astro and tailwindcss
#astro#preact#tailwind-css#viteSubmitted about 2 years agoResponsive landing page using reactjs and tailwind
#react#tailwind-css#viteSubmitted about 2 years agoInteractive card details form using SvelteKit, tailwind and cleavejs
#cube-css#svelte#tailwind-css#viteSubmitted over 2 years agocoming soon page using sveltekit and tailwindcss
#accessibility#svelte#tailwind-cssSubmitted over 2 years ago
Latest comments
- @alexisdlrSubmitted about 2 years ago@codexshellPosted about 2 years ago
Holla! I couldn't help but notice when using firefox to access your browser, the first api request if successful, but firefox ignores subsequent responses from the api. This is because firefox caches responses from the same api for quick reuse. This behavior can be altered by configuring your api requests to prevent browser caching. This is quite simple achieve when using the Fetch API. As an aside, nice animation!
Marked as helpful0 - P@MinamakhloufSubmitted about 2 years ago@codexshellPosted about 2 years ago
Hello there! Noticed a slight glitch with your application. When using firefox browser, firefox is reusing the responses from the first api call. This can easily be fixed by configuring your api requests to prevent browser caching.
Marked as helpful0 - @HsienzSubmitted about 2 years ago@codexshellPosted about 2 years ago
Your website is currently facing a challenge I experienced some time back. Firefox is only using the first response from the api despite multiple requests being sent to the api. A solution around this would be to find a way to disable caching on the tool you are using to make requests. This process is much easier when using the fetch API
Marked as helpful0 - P@rhickey94Submitted over 2 years ago@codexshellPosted over 2 years ago
Holla! Great design. It could use a few extra touches. You could start by finding a way to persist the background color of a rating when selected. Cheers!
0 - @nsnl-coderSubmitted over 2 years ago@codexshellPosted over 2 years ago
Hello. Great design. A final touch would be great. Allow the user to completely deselect a rating altogether in the event they change their minds and do not want to participate in the survey. As per your solution the only way to get rid of the selected state is by refreshing the page. Good luck!
0 - P@Stv-devlSubmitted over 2 years ago@codexshellPosted over 2 years ago
Hey there, great design. Almost perfect. I have a few suggestions I think would be helpful. For starters you could find a way to persist the background color when one selects on a rating. You could also proceed to allowing the user of the component to deselect a rating altogether, in the case they do not want to participate in the survey. Cheers!
Marked as helpful0