-
Notifications
You must be signed in to change notification settings - Fork 6.1k
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.
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
feat: default transition (for colors) to 0.3s
#6726
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
The only visual issue I am seeing is with the language selector. |
Nodejs website use V20 so the error should come from you node version |
Good to note, thanks |
Signed-off-by: Aviv Keller <38299977+RedYetiDev@users.noreply.github.com>
Signed-off-by: Aviv Keller <38299977+RedYetiDev@users.noreply.github.com>
Why is this a fix? What is it fixing? Could you please attach screenshots? |
It's a feature (
N/A
Because it's a transitional effect, screenshots aren't possible, would you like a little video recording? |
Sure; Please add more details explaining why is this needed, what is this improving and before/after videos of what is affecting. |
If I've understood correctly @RedYetiDev you're trying to avoid the flash between the ligh/dark theme? |
Sorry for the delay in my response, yes that is part of the reason, but also other things (like hover effects). I’ll make a video difference soon |
Newscreen-capture.webmOldscreen-capture.1.webm |
I see, I like the changes. But since this changes every page; Please ensure to test every page for inconsistencies or visual bugs this change might introduce. |
Lighthouse Results
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM; I understand the purpose of the changes now. But I'd recommend the author to discretionarily test the website (and all its pages, buttons, etc) to ensure that this change does not introduce issues.
Currently, it introduces one issue (with a weird transition for the language selector), but I'll look for more, than fix what needs to be done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pleas use tailwindcss !transition-none
and duration-300
Enregistrement.de.l.ecran.2024-05-21.a.14.18.11.movAlso there this strange behavior |
The dropdowns are experiencing strange behavior, I need to fix that. Once I do that I'll also move to tailwind |
0.3s
0.3s
I appreciate your thoroughness! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM !
@@ -1,5 +1,6 @@ | |||
* { | |||
@apply subpixel-antialiased; | |||
@apply subpixel-antialiased | |||
transition-colors; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, nice touch! @RedYetiDev I have one concern for users sensitive to this type of interaction, it may be better to use motion-safe:transition-colors
. This feature allows us to control it via the OS settings
https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-reduced-motion
https://tailwindcss.com/docs/hover-focus-and-other-states#prefers-reduced-motion
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice note, seeing as this already landed, a second PR can always change it if needed
Description
This PR sets the default
transition
to0.3s
Validation
To validate whether a transition exists, hover over some elements, and verify a
0.3s
fade from their properties.Check List
npm run format
to ensure the code follows the style guide.npm run test
to check if all tests are passing.npx turbo build
to check if the website builds without errors.