-
Notifications
You must be signed in to change notification settings - Fork 48
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
Event transitions 🎉 #532
Event transitions 🎉 #532
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
As a side note, the Algo event's description escapes the |
Also, can we squash these commits? |
I like have PR revision history. Perhaps maintainer can squash pre-merge? |
Also, this package may be of interest. It does detail-summary animations in-house. Adds a bit of css bloat but simplifies the DOM. |
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.
I have the power to LGTM but won't :)
After looking into it, this doesn't happen with JS enabled. It might be the server-side rendering attempting to sanitize the HTML differently compared to the browser. |
am i missing something or it seem kinda janky to me? |
The behavior or my implementation? |
the behavior |
https://user-images.githubusercontent.com/8981287/189256563-8a2cc082-ccc6-40f3-acef-154185aa3c03.mp4 |
hmm, idk. I just tried to be clever and use the built-in Svelte transitions. It does look weird to me as well. |
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.
I appreciate the changes in this PR because @JustinStitt was able to create an enhancement that gets added to the page progressively when JavaScript is enabled. This means that he took into account backwards-compatibility, allowing the component to properly function even when the expected JavaScript code is absent.
wait hold up, am i the only one that finds this initial jerk kinda weird Screen.Recording.2022-10-05.at.12.58.00.PM.mov |
I am not seeing an initial jerk. It's animation timing is probably a Cubic Bezier with a moderately high starting slope but that is just part of the animation. This is preferred to a slow, unresponsive, and less punchy ease-in timing imo. |
Probably because the animation timing is very low. By doing this change: --- a/src/routes/events/event.svelte
+++ b/src/routes/events/event.svelte
@@ -93,7 +94,7 @@
</noscript>
{#if shown}
- <p class="event-description" transition:slide>
+ <p class="event-description" transition:slide={{ duration: 2000 }}>
{@html info.description}
</p>
{/if} You'll see that the action buttons inside each event are not actually transitioned properly: Screencast.from.05-10-22.15.24.01.webmThis probably explains the initial jerk. |
920b223
to
b58f366
Compare
❌ Deploy Preview for acmcsuf failed.
|
output.mp4 |
pr contains demo
pr contains demo
f9fdd3e
to
273d42b
Compare
* Add transitions to event items * fix event transitions fr Co-authored-by: Ethan Davidson <31261035+EthanThatOneKid@users.noreply.github.com> Co-authored-by: jaasonw <jayywong92@gmail.com>
Demo