# Scroll effect for text

**URL:** <https://forum.8thwall.com/t/scroll-effect-for-text/8132>\
**Category:** Technical Support\
**Tags:** cloud-editor, general, studio\
**Created:** [August 20, 2025, 11:24am UTC](https://forum.8thwall.com/t/scroll-effect-for-text/8132 "2025-08-20T11:24:29Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![GeorgeButler](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.8thwall.com/georgebutler/32/1903_2.png) [@GeorgeButler](https://forum.8thwall.com/u/GeorgeButler)\
**Post date:** [August 20, 2025, 6:34pm UTC](https://forum.8thwall.com/t/scroll-effect-for-text/8132/2 "2025-08-20T18:34:41Z")

</div>

Hi, welcome to the forum!

This is a feature the team has on the radar. In the meantime you might consider splitting up the TOS into sections and having the user click through each section. An example component for this behavior can be found here:

> [@UI Button Click Not Triggering State Change in 8thWall Studio ECS](https://forum.8thwall.com/t/ui-button-click-not-triggering-state-change-in-8thwall-studio-ecs/8105/7):
>
> Hi! I’ve reviewed the code and it looks like some fundamentals are missing. The state machine definitions aren’t quite correct and there’s a number of syntax errors. As a really small example I created this simple component that changes a UI element image to give you an idea how to add listeners in a StateMachine. import \* as ecs from '@8thwall/ecs' ecs.registerComponent({ name: 'Flipbook', schema: { uiElement: ecs.eid, }, schemaDefaults: { }, data: { frame: ecs.i32, }, …

---

_[View the full topic](https://forum.8thwall.com/t/scroll-effect-for-text/8132)._