magicmark
(Mark Willis)
April 12, 2021, 12:50pm
6
magicmark:
Hey @TG2
Thank you for the feedback here, I really appreciate how frustrating it can be when encountering unexpected behaviours.
As Webflow is a tool built on the web standards of HTML, CSS and JS, this is something that exists in a developers world, where manipulating CSS styles with JS will take priority, and therefore having hover interactions with CSS, and hover interactions with JS on the same element, can cause unexpected issues, even more so when using transition: all
It would be great for sure if we highlighted this when a user has CSS interactions on an element, and is about to add an interaction. Honestly, I couldn’t say how straight forward this would be to implement, but it’s worth suggesting.
Please know, that Webflow cannot always prevent users from getting into broken states, Webflow gives users the most freedom it can to manipulate HTML CSS and JS without needing to code, but understanding some fundamentals will always help.
My post isn’t intentionally hidden, it’s left there in the hope that it will help others, which I hope it eventually did.
Best,
Mark
I have zero idea why my post was deleted (by me apparently) 20 seconds after I posted it… first I knew was you calling it out on the other thread. Thanks for pointing it out.
Here it is again
2 Likes