I’ve run into a bug I cant seem figure out. I found someone with a similar problem last year, but there was no answer.
I launched a site last month and everything was working well. I was recently notified that certain text elements were no longer displaying on mobile, despite no changes being made since launch.
I was able to figure out that it seems to be animations that are causing the display issue. Remove any animation, the text displays. Reactivate them, the text disappears. – This only seems to be affecting actual mobile devices, as everything displays correctly elsewhere, including mobile-sized previews/browsers.
I’d like to keep the animations as they are. As I said, they’ve worked until recently. What am I missing here?
When elements disappear during animations on mobile devices, there are two main solutions to consider:
For mobile-specific issues, you can disable animations on smaller screens while keeping them active on desktop. To do this, navigate to the element’s animation settings and adjust the viewport conditions under “Advanced Settings.”
For text visibility issues across all devices, check the overflow settings of the parent elements. Set the parent container’s overflow to “visible” in the Style panel to ensure animated text remains visible throughout the animation sequence.
Hopefully this helps! If you still need assistance, please reply here so somebody from the community can help.
I’d prefer to find a solution to keep the animations on mobile. It doesn’t make sense that some animations are fine and others just randomly quit working after working previously.
Hello @rmounts,
I inspected your website on my iphone and the issue comes from this code you have on your page settings head
I don’t know why you are using that, because by default the body behaves like that and you can apply the overflow to another element. Anyway, if you remove the height 100% from that code your website animations should work again. I hope this helps!
Wow! I didn’t realize that was there, and am honestly not too sure where it even came from. Best guess would be it was left over from something we cleared out from many iterations ago.
