-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Fix sliding animation on table elements in Safari #5922
Fix sliding animation on table elements in Safari #5922
Conversation
When will the release be released? |
This is a proof-of-concept commit for comments. It is not yet cleaned up.
7e2b03a
to
153a116
Compare
Added a test and cleaned up the PR. |
@benmccann is attempting to deploy a commit to the Svelte Team on Vercel. A member of the Team first needs to authorize it. |
Just ran into #4948 and found this old open PR. Would it be useful for somebody to dust it off and get it ready to merge? If not, it would be lovely if it was closed w/ a rejection reason. |
Yeah, as far as I'm aware, the main reasons it hasn't been reviewed is because there are merge conflicts and it's buried down the queue. Sending a cleaned up version would address both of those issues |
This is a proof-of-concept PR for comments. It is not yet cleaned up. See below for what's incomplete.
This PR fixes #4712 and fixes #4948 .
The approach is as follows:
staticCss
in this PR) that is present throughout animationFor #4712 : Since the
overflow
property's Animation type isdiscrete
, the behavior is actually defined as changing overflow at the 50% mark if it wasn'toverflow: hidden
to begin with. However, the sliding animations require thatoverflow: hidden
throughout the animation. This PR moves theoverflow: hidden
into astaticCss
which is applied throughout the animation.For #4948 : The
display
property is not animatable, so it can't be applied through animation keyframes. This PR adds adisplay: block
if it detects that the element'sdisplay
property contains `table. It could instead use a whitelist but I wanted to keep this simple and address #4948 before attempting to address all scenarios that the display property.I didn't think this was a large enough change to warrant an rfc. Please let me know if it is.
PR is now ready for review.
I plan to add tests since this behavior adds an additional step to animations and needs to be tested.
Tests
npm test
and lint the project withnpm run lint