> I'm not even sure I can do this with requestWindowAnimationFrame Why not?

Well, at first I was thinking about doing this in a side-effect. More precisely, I would write a function that manipulates the DOM, i,e, changes the number value, inside requestWindowAnimationFrame and execute that function in an effect handler. However, that feels weird to me because I would mess around with the DOM outside of react/reagent, which works and is in this case just a minor issue but it also feels like having state outside of re-frame. There is some risk here. I'll just try and see if it works.

> feels like having state outside of re-frame Would you consider this a state though? Something being displayed on screen doesn't necessarily mean that it's a part of the state. It makes even more sense in my mind when I think of a client with a 60 Hz monitor and a client with a 200 Hz one. With the current animation frame being considered a part of the app's state, such clients could never have the same app, except for the 0th frame.

Interesting point. Still feels weird to trigger this change outside of reagent re-frame but I think it's exactly how this is meant to be used.

You can trigger it within Reagent though, just outside of re-frame. But see what works best in your case.

I'll see

I thought about doing it within reagent but that isn't very nice with my use case.