While working on another article, I stumbled upon a fascinating discovery: a way to manipulate and read state solely through style rules using HTML and CSS.

This admittedly outrageous hack builds upon one realization: Scroll containers can hold state in their scroll position. This state can be set using scroll-snap, and read using scroll-driven animations.

We can use a single div with style rules to write, store and read a state.

⚠️ Important Note: This technique I’m about to describe is an experimental, admittedly outrageous hack. While it’s an intriguing concept and might open up new possibilities for CSS and HTML, it’s not recommended to use this in a production environment. To stress this point: this is a hack. It might never be “production-ready” as we typically understand it.

It’s worth noting that this technique — and the examples provided below — currently work exclusively in Chrome Canary and other browsers that support scroll-driven animations. Also, it’s important to acknowledge that the implications of this technique on accessibility and performance have not been investigated. Please treat it as a fascinating discovery and a basis for further exploration rather than a ready-to-go solution.

Ideally, we’d have a formalized feature akin to the proposed CSS Toggles, as detailed in this GitHub issue and unofficial proposal draft by Tab Atkins Jr. and Miriam E. Suzanne.

Let’s dive into the details.

Maintaining state

Storing state can be achieved by using a simple <div> element, and converting it into a scroll container using overflow-x: scroll. To give it scrollable overflow, we add a pseudo-element to the div, placing it just outside the scroll-port.

The scroll position constitutes our state. Specifically, the scroll container is in one state when scrolled to the start, and another when scrolled to the end. Visually, the state element takes on a red background color when the container is scrolled to the start, and transitions to green when scrolled to the end.

Note: Here, our scroll position holds a binary state - at the start or at the end. But with the use of multiple snap points, it’s possible to switch between more than two values

Our initial scroll state element.
The element must currently be scrolled manually to toggle the 'state'. 
.state {
    display: flex;
    width: 80px;
    height: 30px;
    border-radius: 15px;
    overflow-x: scroll;

    &::before, &::after {
        content: '';
        display: block;
        flex: none;
        width: 100%;
        height: 100%;
    }

    &::after {
        background: green;
    }
}

Altering State with Scroll-Snap

Now that we’ve got an element maintaining our state through its scroll position, we can attempt to modify this state.

The scroll position, and thereby the state, can be changed temporarily through the application of scroll-snap. Notably, the state remains preserved even after removing the scroll snapping declarations.

For illustrative purposes, in our example, we trigger scroll-snap on hover. Nevertheless, for more complex scenarios, space-toggles or cyclic-toggles can come in handy.

Try hovering the element to toggle the 'state'. 
.state {
    /* ... */
    scroll-snap-type: x mandatory;
    /* ... */
    &:hover::after {
        scroll-snap-align: end;
    }
}

Reading the state

Awesome, we now have a mechanism to store and set the state. But, how do we read this state?

With the advent of scroll-driven animations, we can use these as a means to interpret the state. We can employ either a view-timeline or a scroll-timeline to expose the state’s value, and with the use of timeline-scope, we can even elevate it to the root element if necessary.

I’ll use cyclic toggles to read the state as I think that’s neat, but there are many ways to read out the state, either by using space-toggles or setting properties directly in the animation keyframes.

Note: Just as we can use multiple snap points to switch between more than two values, cyclic toggles aren’t restricted to binary states. As pointed out by Roman, they can play really well when we have multiple possible values.

⚠ This demo requires support scroll-driven animations with timeline-scope. Try it out in Chrome Canary.
Try hovering the element to toggle the 'state'. 
@keyframes read-state {
    contain 0% {
        --state: var(--state--off);
    }
    contain 100% {
        --state: var(--state--on);
    }
}

.state {
    /* ... */
    &::after {
        view-timeline: --state-timeline inline;
    }
}

.use-state {
    --state: var(--state--off);
    --state--off: var(--state, );
    --state--on: var(--state, );
    height: 100px;
    timeline-scope: --state-timeline;
    animation: read-state;
    animation-timeline: --state-timeline;
    background: var(--state--off, pink) var(--state--on, palegreen);
}

Manipulating the state trough custom properties

While directly writing the state with scroll-snap is effective, it can be a bit unwieldy. A smoother alternative can be achieved by exposing custom properties, which would then allow us to manipulate the state using space-toggles instead.

In this case, we will use --write-state-on: ; to switch the state to on and --write-state-off: ; to transition the state to off. This method allows us to manipulate the state externally, outside the confines of the state element itself.

.state {
    /* ... */
    &::before {
        scroll-snap-align: var(--write-state-off) start;
    }
    &::after {
        scroll-snap-align: var(--write-state-on) end;
    }
}
ON
OFF
⚠ This demo requires support scroll-driven animations with timeline-scope. Try it out in Chrome Canary.
Try hovering the ON and OFF elements to toggle the 'state'.

Trigger a state change using another scroll-timeline

Now that we’ve delved into the depths of this outrageous hack and demonstrated that it’s possible to trigger the state change from outside the state element itself, we can even go one step further.

Yes, brace yourself — we can trigger this state change from another scroll-driven animation. In theory, we could use this to trigger a scroll-based animation once — tempting, right? But remember: just because you can do something, doesn’t mean you should.

⚠ This demo requires support scroll-driven animations with timeline-scope. Try it out in Chrome Canary.
Scroll down in the pink container to trigger a state change. 

@keyframes write-state {
    100% {
        --write-state-on: ;
    }
}

.read-and-write-state {
    --state: var(--state--off);
    --state--off: var(--state, );
    --state--on: var(--state, );
    display: grid;
    height: 100px;
    grid-template-rows: 200px;
    overflow-y: scroll;
    timeline-scope: --state-timeline;
    animation: write-state, read-state;
    animation-timeline: scroll(self block), --state-timeline;
    background: 
        var(--state--off, pink)
        var(--state--on, palegreen);
}

Acknowledgments

This exploration would not have been possible without the inspiration and groundbreaking work of many brilliant individuals in the field. I would like to express my gratitude to:

  • The team behind CSS Day, whose event sparked my curiosity and led me down this fascinating path.
  • Roman Komarov, who introduced us to the wonders of Cyclic Toggles.
  • Lea Verou and Ana Tudor, among others, who unveiled the power and potential of Space Toggles.
  • Bramus, who cleverly found a way to hack modern CSS into supporting Scroll Triggered Animations.

Their contributions have significantly enriched our understanding of CSS and its capabilities. I am in awe of their ingenuity and thankful for their shared knowledge.

TL;DR;

With the advent of scroll-driven animations we can store, write and read state from a single div. I’m not sure this is a good idea, but I think it’s a neat discovery.