little teaser: we think jae just figured out what the underlying issue with the "some pages loop sometimes" probably aka "double timeline" probably aka "followers go sideways" bug was
similar to the random page switching bug, sometimes you read the docs and immediately know where you went wrong
If the optional
replaceNodeparameter is provided, it must be a child ofcontainerNode.
folks you will never fucking guess what isn't a child of containerNode
this fix is now live! knocked out at least three reported bugs with this one (maybe more, i admit i was only skimming the bug list to figure out which ones i was handling).
please let us know if you're still seeing looping pages, non-interactive elements, sideways timelines, etc. these bugs can be hard to reproduce consistently so sometimes we're only giving our best guess as to whether or not they're actually fixed, although in this case i'm actually extremely confident.
