Have a slightly odd case here that's got me stumped. I've written a fairly extensive sugarcube-based story - essentially a display framework written on top of the twine/SC base - which I am currently polishing up for release. It all runs smoothly except for one DOM replace passage, which for some reason hiccups on execution.
I wanted to figure out why and implemented a few performance.now() cases to test execution speed; not sure which part of the object handling is causing the slowdown but I'm pretty sure it's related to deeply nested objects & iterations somewhere in the code.
Only, when I execute the code with the timer elements in place, it executes smoothly (tested on FF and Chrome). Without them it lags visibly as the element is replaced.
Can't make heads or tails of this. Anyone have any ideas?