You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most of the time entrances need to be timed with other entrances. Using delay- is a decent workaround, but in Tailwind land, you're immediately limited by the number of delay classes. It'd be great if there was a first party API for handling sequences.
Potential directive API:
x-breeze-sequence: a string representing the sequence this element belongs to
x-breeze-sequence-position: the position in the sequence for this element
<h1class="transition duration-200"
x-breeze-from="opacity-0"
x-breeze-sequence="someUniqueIdentifier"
x-breeze-sequence-position="1"
>
This one will kick off a sequence.
</h1><h1class="transition duration-200"
x-breeze-from="opacity-0 translate-y-5"
x-breeze-sequence="someUniqueIdentifier"
x-breeze-sequence-position="2"
>
This one will schedule it's transition after the first element has completed.
</h1>
The text was updated successfully, but these errors were encountered:
Most of the time entrances need to be timed with other entrances. Using
delay-
is a decent workaround, but in Tailwind land, you're immediately limited by the number of delay classes. It'd be great if there was a first party API for handling sequences.Potential directive API:
x-breeze-sequence
: a string representing the sequence this element belongs tox-breeze-sequence-position
: the position in the sequence for this elementThe text was updated successfully, but these errors were encountered: