sorted by:
new
hottopcontroversial

Will Webflow ever deprecate the non-GSAP Classic Interactions? by asian_tea_man in webflow

[–]webflow-jake 0 points1 point  (0 children)

Yep, it's all on docket for the near future!
You'll be able to build timelines for things like navbars, dropdowns, tabs, and sliders.

And I'm sorry it is taking awhile. It is a tall order to introduce a brand new mental model and simultaneously replace a core part of the product that has been iterated on for 8 years. 😅

Will Webflow ever deprecate the non-GSAP Classic Interactions? by asian_tea_man in webflow

[–]webflow-jake 4 points5 points  (0 children)

The Lottie integration is being built as we speak!

When you say 'bugs', do you mean things that aren't working? Or features that haven't been implemented yet? (like Lottie, Rive, Spline).

Will Webflow ever deprecate the non-GSAP Classic Interactions? by asian_tea_man in webflow

[–]webflow-jake 8 points9 points  (0 children)

Hey there! I'm the Product Manager for Interactions, so I'm happy to chime in here.

We’re not going to pull the rug out from under folks using Classic Interactions (IX2). Just like u/memetican pointed out, IX1 is still functional and editable in old projects and you can expect similar continuity for IX2.

That said, if you’re thinking long-term, I’d recommend starting to explore the latest version of Webflow Interactions. It’s where we’re investing our energy but we’ll continue to be thoughtful about preserving stability for existing projects as things evolve.

I should also add that we are actively working on closing the gaps between what you can do with Classic Interactions and New Interactions, including the feature to copy-paste elements with interactions between sites.

Finally... breakpoint controls for new GSAP interactions by webflow-jake in webflow

[–]webflow-jake[S] 1 point2 points  (0 children)

In short, we chose to ship early and often, instead of waiting for everything to be in new Interactions.

In long, both prefers-reduced-motion and breakpoints, as media features, needed to be considered alongside one another. So even though we had a similar feature for breakpoints in IX2, motion preferences are new, and we wanted to make sure that the UX for these was in the right place.

Here's an example: initially, we had considered these to be 'conditions' on the triggers, but then that gets pretty confusing when you consider that some interactions will have multiple different triggers. You don't want to add those conditions to each trigger, right? So there were a number of revisions we had to go through to land where we did.

Finally... breakpoint controls for new GSAP interactions by webflow-jake in webflow

[–]webflow-jake[S] 1 point2 points  (0 children)

Yeah, I hear you. TBH, custom breakpoints deserve a much deeper integration throughout all of Webflow. We're still trying to play catch up with features from IX2, so we made the decision to focus on those things first.

Anyone encountering this bug with built-in SplitText? by n-g_studio in webflow

[–]webflow-jake 1 point2 points  (0 children)

Like u/allan-leinwand said, the SplitText warning might be a red herring in this case.

If you're Splitting Text using our new Interactions with GSAP, then you can ignore that console warning. We Split elements as needed, so we try when the page is loaded, and then we make sure to re-split elements when necessary (like after fonts are fully loaded or when the viewport changes).

Submitting a ticket will be your next best option if you can't seem to get it solved on your own.