A little more info on this change:
For v-synced rendering the runtime calls a function to request the next frame (requestAnimationFrame). Previously the runtime would run its entire tick logic, and request the next frame right at the end of that. Now in r198 the very first thing it does each tick is request the next frame, then go ahead and process that tick's logic.
This should in theory give the browser more time to accurately schedule frames. Consider an intense game where the logic takes 15ms. If the runtime requests the next frame at the end of the tick, the browser has just 1ms to schedule the frame in time. Now that the runtime requests the next frame at the beginning of the tick, it has the full 16ms frame to schedule the next frame in time. This could improve the predictability/stability of the framerate.
TBH I don't know much about the internals of browser frame scheduling, and it's difficult to know for sure if this helps, so it was kind of an experimental change. It seems to be a good idea though and feedback seems to be either no change or positive, so I think we'll keep it!