using RS with RTF, regarding the (known) frameloop issue

[ssadler]

Hi, I ran into #1586 in my application, and I wanted to understand better in what circumstances it's triggered to see if I can avoid it.

The strange thing is that at some point it was working fine, without the Globals.assign({ frameLoop: 'always' }) workaround. But at some point, the use of RS in one of my regular HTML components stopped working unless I manually provoked the updates by moving the mouse. I identified the commit in my project where the bug appeared, and I couldn't figure out what change was triggering it, it's a bit of a mystery.

So, I want to understand what was the difference at the point when the bug was not happening, what was that reason that they were coexisting. I did not change anything about the render loop, I have always had frameloop="demand" in the RTF Canvas.

I'm using @react-spring/web in my HTML components, and RTF. I do also use useSpring from react-spring inside the RTF context, but the bug persists even if I remove it.

I'm trying to avoid using the Globals workaround because of the messages that get logged in the console which make debugging difficult sometimes.

Many thanks!