fix: remove slide animations from Dialog due to unexpected behavior #7114
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #6649, where the default
AlertDialog
andDialog
component exhibited unexpected diagonal slide animations upon opening and closing.The reasons for removing these specific slide animations are:
tailwindcss-animate
andtw-animate-css
).AlertDialog
orDialog
, which does not feature this diagonal sliding effect. This inconsistency can be confusing for users.new-york-v4
style components installed via the CLI for Tailwind v4 projects) seem to omit these specific slide animations forAlertDialog
. Removing them from the base styles promotes consistency and gives users the explicit choice to add custom motion if desired, rather than removing an unexpected default animation.To resolve this, the following classes have been removed from
AlertDialogContent
andDialogContent
in bothdefault
andnew-york
styles:data-[state=closed]:slide-out-to-left-1/2
data-[state=closed]:slide-out-to-top-[48%]
data-[state=open]:slide-in-from-left-1/2
data-[state=open]:slide-in-from-top-[48%]
The remaining
fade-*
andzoom-*
animations provide a clean, centered open/close transition.